mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Keith Busch <keith.busch@intel.com>,
	<linux-block@vger.kernel.org>
Subject: Re: [GIT PULL] NVMe changes for 4.5-rc1
Date: Fri, 22 Jan 2016 09:29:37 -0700	[thread overview]
Message-ID: <56A258F1.1060207@fb.com> (raw)
In-Reply-To: <CA+55aFwy5YJdV5Xk_Mj1niWUQeUbXUS6igNZBw710cibQfY48A@mail.gmail.com>

On 01/22/2016 09:26 AM, Linus Torvalds wrote:
>
> On Jan 22, 2016 7:59 AM, "Jens Axboe" <axboe@fb.com
> <mailto:axboe@fb.com>> wrote:
>  >>
>  >>   - nvme_dev_remove() got renamed to nvme_remove_namespaces(), but also
>  >> lost the "dev" argument (it takes "struct nvme_ctrl *ctrl" now).
>  >
>  > &dev->ctrl
>
> That's not the problem - the code does that already.
>
> But we want the dev argument *back*, since the function now wants to do
> that nvme_io_incapable() check and then cancel the IO on it.
>
> And I didn't know if you guys would want to use container_of() or just
> change the calling convention back to using "dev", or perhaps just
> decide to do the IO cleanup in the caller instead. That last option
> seems the cleanest, since now nvme_dev_remove_namespaces() is just about
> the namespace, and maybe it would be better to re-introduce a whole new
> nvme_dev_remove() that does the old thing.

The latter is the cleanest approach, we'll get it fixed up.

> So I decided to not do anything at all, and just let you guys sorry it
> out instead.

Is that like a Canadian duel?

-- 
Jens Axboe

      parent reply	other threads:[~2016-01-22 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21 21:27 Jens Axboe
2016-01-22  3:58 ` Linus Torvalds
2016-01-22 15:58   ` Jens Axboe
     [not found]     ` <CA+55aFwy5YJdV5Xk_Mj1niWUQeUbXUS6igNZBw710cibQfY48A@mail.gmail.com>
2016-01-22 16:29       ` Jens Axboe [this message]

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=56A258F1.1060207@fb.com \
    --to=axboe@fb.com \
    --cc=keith.busch@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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

Powered by JetHome