From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme update for Linux 4.14
Date: Mon, 28 Aug 2017 10:03:39 -0600 [thread overview]
Message-ID: <44a35d51-48d5-7181-df7e-b75fcbc053d9@kernel.dk> (raw)
In-Reply-To: <20170828155925.GA32254@infradead.org>
On 08/28/2017 09:59 AM, Christoph Hellwig wrote:
> On Mon, Aug 28, 2017@09:55:55AM -0600, Jens Axboe wrote:
>>> It was based on the nvme-3.13 tree from about two weeks ago,
>>> which was based on your for-linus at about that time.
>>
>> Changes for 4.14 should be against the 4.14 branch. for-linus is
>> for 4.13. In any case, there will be a conflict against master...
>
> We would have otherwise had conflicts against changes in Linus'
> tree for 4.13, so we were between a rock and a hard place here.
But one rock is shittier than the other. If you based it against
4.14, then at least I only have to resolve the the problem once.
The real problem is that the patch that went into master had
cleanups too. You should push back against that, since it will
inevitably cause problems by diverging 4.13 and 4.14 more than
absolutely necessary. Having conflicts in nvme for the block tree
is not isolated to this series, unfortunately.
--
Jens Axboe
next prev parent reply other threads:[~2017-08-28 16:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 14:33 [GIT PULL] nvme update for Linux 4.14 Christoph Hellwig
2017-08-28 15:51 ` Jens Axboe
2017-08-28 15:53 ` Christoph Hellwig
2017-08-28 15:55 ` Jens Axboe
2017-08-28 15:59 ` Christoph Hellwig
2017-08-28 16:03 ` Jens Axboe [this message]
2017-08-28 17:57 ` Christoph Hellwig
2017-08-28 18:05 ` Jens Axboe
2017-08-28 18:40 ` Christoph Hellwig
2017-08-28 19:01 ` Jens Axboe
2017-08-28 19:43 ` Christoph Hellwig
2017-08-28 19:56 ` Sagi Grimberg
2017-08-29 14:34 ` Jens Axboe
2017-08-29 14:50 ` Christoph Hellwig
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=44a35d51-48d5-7181-df7e-b75fcbc053d9@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