From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [GIT PULL] Block core changes for 4.10
Date: Tue, 13 Dec 2016 13:19:21 -0700 [thread overview]
Message-ID: <e2104bea-8028-dafe-cb64-e376fa7e45fb@kernel.dk> (raw)
In-Reply-To: <6176de36-7f4f-040b-f277-e872cc98eb5e@kernel.dk>
On 12/11/2016 06:52 PM, Jens Axboe wrote:
> Note that this pull will throw 3 trivial merge conflicts, since we had
> patches that went into mainline after 4.9-rc1 (upon which this branch is
> based), and one that will not show up in block/blk-flush.c. The latter
> is due to a fix that went in for the flush code using an old request
> flag that is now changed to a per-request one. To ensure that this all
> goes smoothly, I just merged 4.9 with this branch and provide that as a
> reference:
>
> git://git.kernel.dk/linux-block.git for-4.10/merge
>
> But really, the only one you to watch for is this line in
> block/blk-flush.c:
>
> /* for avoiding double accounting */
> rq->cmd_flags &= ~REQ_STARTED;
>
> which should now be:
>
> rq->rq_flags &= ~RQF_STARTED;
>
> and the three merge conflicts that do show up are trivially resolvable.
Since you have merged trees since that contain block drivers, you are
going to get a new merge conflict. There's one with mmc block now, which
is again just a switch from rq->cmd_flags to rq->rq_flags and using
RQF_foo instead of REQ_foo.
--
Jens Axboe
next prev parent reply other threads:[~2016-12-13 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 1:52 [GIT PULL] Block core changes for 4.10 Jens Axboe
2016-12-13 20:19 ` Jens Axboe [this message]
2016-12-13 23:31 ` Stephen Rothwell
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=e2104bea-8028-dafe-cb64-e376fa7e45fb@kernel.dk \
--to=axboe@kernel.dk \
--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.