From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH][linux-block] NVMe: Fix FS mount issue(hot-remove followed by hot-add)
Date: Fri, 12 Dec 2014 08:57:41 -0700 [thread overview]
Message-ID: <548B1075.5000304@kernel.dk> (raw)
In-Reply-To: <000d01d015e8$5615a740$0240f5c0$@samsung.com>
On 12/12/2014 01:47 AM, Indraneel Mukherjee wrote:
>> -----Original Message-----
>> From: Linux-nvme [mailto:linux-nvme-bounces at lists.infradead.org] On Behalf
>> Of Jens Axboe
>> Sent: Thursday, December 11, 2014 8:56 PM
>> To: Indraneel M; linux-nvme at lists.infradead.org; Keith Busch
>> Subject: Re: [PATCH][linux-block] NVMe: Fix FS mount issue(hot-remove
>> followed by hot-add)
>>
>> On 12/11/2014 03:47 AM, Indraneel M wrote:
>>> Jens, this version is against the linux-block tree.
>>
>> It's not, though:
>>
>> checking file drivers/block/nvme-core.c
>> Hunk #1 FAILED at 2600.
>> Hunk #2 FAILED at 2859.
>> 2 out of 2 hunks FAILED
>>
>> what branch are you on? It has to be against for-3.19/drivers or for-next.
> This
>> was simple enough to hand apply, so I did that. This is the result:
>>
>> http://git.kernel.dk/?p=linux-
>> block.git;a=commit;h=285dffc9101244ac65c29672a1fb3fe614b52238
>
>
> Thanks Jens! I had just cloned linux-block and created a patch against it
> without any branch switch.
It's not easy to know... Generally, if we're before a merge window,
patches should be sent against for-3.x/drivers, where x is the next
release. If we're after a merge window and it needs to go into this
version, then patches should be against for-linus (which is generally
pretty close to master).
--
Jens Axboe
prev parent reply other threads:[~2014-12-12 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 10:47 [PATCH][linux-block] NVMe: Fix FS mount issue(hot-remove followed by hot-add) Indraneel M
2014-12-11 15:26 ` Jens Axboe
2014-12-12 8:47 ` Indraneel Mukherjee
2014-12-12 15:57 ` 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=548B1075.5000304@kernel.dk \
--to=axboe@kernel.dk \
/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