Hi David,
On Sun, 2019-02-10 at 18:46 +0100, David Kozub wrote:
> On Fri, 8 Feb 2019, Derrick, Jonathan wrote:
>
> > On Mon, 2019-02-04 at 23:44 +0100, David Kozub wrote:
> > > On Mon, 4 Feb 2019, Christoph Hellwig wrote:
> > >
> > > > > + /* first do a discovery0 */
> > > > > + error =
On Fri, 8 Feb 2019, Derrick, Jonathan wrote:
On Mon, 2019-02-04 at 23:44 +0100, David Kozub wrote:
On Mon, 4 Feb 2019, Christoph Hellwig wrote:
+ /* first do a discovery0 */
+ error = opal_discovery0_step(dev);
+ for (state = 0; !error && state < n_steps; state++)
+
On Mon, 2019-02-04 at 23:44 +0100, David Kozub wrote:
> On Mon, 4 Feb 2019, Christoph Hellwig wrote:
>
> > > + /* first do a discovery0 */
> > > + error = opal_discovery0_step(dev);
> > >
> > > + for (state = 0; !error && state < n_steps; state++)
> > > + error = execute_step(dev, &steps[
On Mon, 4 Feb 2019, Christoph Hellwig wrote:
+ /* first do a discovery0 */
+ error = opal_discovery0_step(dev);
+ for (state = 0; !error && state < n_steps; state++)
+ error = execute_step(dev, &steps[state], state);
+
+ /*
+* For each OPAL command
> + /* first do a discovery0 */
> + error = opal_discovery0_step(dev);
>
> + for (state = 0; !error && state < n_steps; state++)
> + error = execute_step(dev, &steps[state], state);
> +
> + /*
> + * For each OPAL command the first step in steps starts some sort of
Originally each of the opal functions that call next include
opal_discovery0 in the array of steps. This is superfluous and
can be done always inside next.
Signed-off-by: David Kozub
Reviewed-by: Scott Bauer
---
block/sed-opal.c | 89 +++-
1 file chan
6 matches
Mail list logo
