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

On 01/21/2016 08:58 PM, Linus Torvalds wrote:
> On Thu, Jan 21, 2016 at 1:27 PM, Jens Axboe <axboe@fb.com> wrote:
>>
>> Note that pulling this in will conflict with master, since the code was
>> forked off pretty early, and we had a good chunk of nvme fixes later in
>> the 4.4 cycle.
>
> Not just conflict, but conflict in bad ways. I don't think I'll be
> able to fix it up sanely.
>
> In particular, commit b5875222de2f ("NVMe: IO ending fixes on surprise
> removal") by Keith Busch added this to nvme_dev_remove():
>
>      if (nvme_io_incapable(dev)) {
>          /*
>           * If the device is not capable of IO (surprise hot-removal,
>           * for example), we need to quiesce prior to deleting the
>           * namespaces. This will end outstanding requests and prevent
>           * attempts to sync dirty data.
>           */
>          nvme_dev_shutdown(dev);
>      }
>
> and in your branch we now have:
>
>   - nvme_dev_shutdown() is now nvme_dev_disable(dev, false). Fine.
>
>   - nvme_dev_remove() got renamed to nvme_remove_namespaces(), but also
> lost the "dev" argument (it takes "struct nvme_ctrl *ctrl" now).

&dev->ctrl

> I think I will end up doing the merge by just dropping that part of
> the surprise removal commit, and letting you and Keith work out what
> the real solution is..

That's fine, thanks for merging!

-- 
Jens Axboe

  reply	other threads:[~2016-01-22 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21 21:27 [GIT PULL] NVMe changes for 4.5-rc1 Jens Axboe
2016-01-22  3:58 ` Linus Torvalds
2016-01-22 15:58   ` Jens Axboe [this message]
     [not found]     ` <CA+55aFwy5YJdV5Xk_Mj1niWUQeUbXUS6igNZBw710cibQfY48A@mail.gmail.com>
2016-01-22 16:29       ` Jens Axboe
2016-01-22 22:08         ` Keith Busch
2016-01-22 22:16           ` Keith Busch

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=56A251C2.101@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.