From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [PATCH] fix failure with new bi_error field of bio
Date: Fri, 16 Oct 2015 13:31:52 +0200 [thread overview]
Message-ID: <20151016113152.GS32439@soda.linbit> (raw)
In-Reply-To: <1444983195-12439-1-git-send-email-nwang@suse.com>
On Fri, Oct 16, 2015 at 04:13:15PM +0800, Nick Wang wrote:
> drbd fail to build with new bio structure and interface
> after 4.3.0, see 4246a0b63bd8f56a1469b12eafeb875b1041a451
Yes.
*out-of-tree* drbd, as is in public git right now, that is.
> CC: linux-kernel@vger.kernel.org
No reason to CC linux-kernel, they won't care for out-of-tree drivers.
And the in-tree ones are adjusted to new infrastructure on-the-go,
whenever infrastructure changes. So that's all been done already.
But thanks.
Lars
--
: Lars Ellenberg
: http://www.LINBIT.com | Your Way to High Availability
: DRBD, Linux-HA and Pacemaker support and consulting
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
next prev parent reply other threads:[~2015-10-16 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 8:13 [Drbd-dev] [PATCH] fix failure with new bi_error field of bio Nick Wang
2015-10-16 11:31 ` Lars Ellenberg [this message]
2015-10-19 0:00 ` [Drbd-dev] 答复： " Nick Wang
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=20151016113152.GS32439@soda.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.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