From: Jens Axboe <axboe@kernel.dk>
To: Philipp Reisner <philipp.reisner@linbit.com>,
linux-kernel@vger.kernel.org
Cc: drbd-dev@lists.linbit.com, Lai Jiangshan <laijs@cn.fujitsu.com>,
Michel Lespinasse <walken@google.com>
Subject: Re: [PATCH 0/2] More for the 3.18 merge window
Date: Thu, 18 Sep 2014 09:00:56 -0600 [thread overview]
Message-ID: <541AF3A8.3000900@kernel.dk> (raw)
In-Reply-To: <1411051782-23375-1-git-send-email-philipp.reisner@linbit.com>
On 2014-09-18 08:49, Philipp Reisner wrote:
> Hi Jens,
>
> please put these two patches into your for-3.18/drivers branch. They fix
> the safety code for concurrent overlapping write detection in a DRBD
> dual primary setup.
>
> The first of those two should also go to the stable kernels, I marked it
> with CC: stable@kernel.org
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2014-09-18 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 14:49 [PATCH 0/2] More for the 3.18 merge window Philipp Reisner
2014-09-18 14:49 ` [PATCH 1/2] drbd: compute the end before rb_insert_augmented() Philipp Reisner
2014-09-18 14:49 ` [PATCH 2/2] drbd: use RB_DECLARE_CALLBACKS() to define augment callbacks Philipp Reisner
2014-09-18 15:00 ` 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=541AF3A8.3000900@kernel.dk \
--to=axboe@kernel.dk \
--cc=drbd-dev@lists.linbit.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.reisner@linbit.com \
--cc=walken@google.com \
/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