> Ping on this series. Rob, I think I've addressed all your feedback.
> Can you please verify?
I haven't tested it, but it reads OK. I'm OK with just extending
the valid count for bits set to one for now; we can add a new
argument later if a need arises for extending it to express new bits
set t
On Fri, May 25, 2018 at 08:51:22PM +0300, Michael S. Tsirkin wrote:
> On Mon, May 21, 2018 at 10:31:59AM -0600, Ross Zwisler wrote:
> > Changes since v3:
> > * Updated the text in docs/nvdimm.txt to make it clear that the value
> >being passed in on the command line in an integer made up of va
Ping on this series. Rob, I think I've addressed all your feedback. Can you
please verify?
Thanks,
- Ross
On Mon, May 21, 2018 at 10:31:59AM -0600, Ross Zwisler wrote:
> Changes since v3:
> * Updated the text in docs/nvdimm.txt to make it clear that the value
>being passed in on the comman
On Mon, May 21, 2018 at 10:31:59AM -0600, Ross Zwisler wrote:
> Changes since v3:
> * Updated the text in docs/nvdimm.txt to make it clear that the value
>being passed in on the command line in an integer made up of various
>bit fields. (Rob Elliott)
>
> * Updated the "Highest Valid Cap
Changes since v3:
* Updated the text in docs/nvdimm.txt to make it clear that the value
being passed in on the command line in an integer made up of various
bit fields. (Rob Elliott)
* Updated the "Highest Valid Capability" byte to be dynamic based on
the highest valid bit in the user'
