Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH][linux-block] NVMe: Fix FS mount issue(hot-remove followed by hot-add)
Date: Thu, 11 Dec 2014 08:26:09 -0700	[thread overview]
Message-ID: <5489B791.7020007@kernel.dk> (raw)
In-Reply-To: <1418294839-3464-1-git-send-email-indraneel.m@samsung.com>

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

-- 
Jens Axboe

  reply	other threads:[~2014-12-11 15:26 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 [this message]
2014-12-12  8:47   ` Indraneel Mukherjee
2014-12-12 15:57     ` Jens Axboe

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=5489B791.7020007@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