Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jonathan.derrick@intel.com (Jon Derrick)
Subject: [PATCH] NVMe: Expose namespace unique identifier to sysfs
Date: Tue, 8 Dec 2015 12:25:57 -0700	[thread overview]
Message-ID: <20151208192557.GA3890@localhost.localdomain> (raw)
In-Reply-To: <20151208191555.GB16241@localhost.localdomain>

> > I'm a bit reluctant to use bitmap_empty here, because it's not actually
> > a bitmap.  We almost want the inverse of memchr ("find me the first
> > byte that is non-zero").  Maybe somebody else knows a better functoin
> > to call here?
> 
> Better methods are learned all the time! It was nearly a year ago today
> you suggested bitmap_empty for checking the very same fields. :)
> 

How about memchr_inv? I think Matthew was alluding to that one

  reply	other threads:[~2015-12-08 19:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 17:26 [PATCH] NVMe: Expose namespace unique identifier to sysfs Keith Busch
2015-12-08 18:53 ` Matthew Wilcox
2015-12-08 19:15   ` Keith Busch
2015-12-08 19:25     ` Jon Derrick [this message]
2015-12-08 23:11     ` Christoph Hellwig
2015-12-09  8:12     ` Dan Williams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151208192557.GA3890@localhost.localdomain \
    --to=jonathan.derrick@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox