From: Philipp Reisner <philipp.reisner@linbit.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jens Axboe <jens.axboe@oracle.com>,
drbd-dev@lists.linbit.com, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org,
Nikanth Karthikesan <knikanth@suse.de>
Subject: Re: linux-next: drbd tree build failure
Date: Tue, 15 Sep 2009 16:03:23 +0200 [thread overview]
Message-ID: <200909151603.24843.philipp.reisner@linbit.com> (raw)
In-Reply-To: <20090915165309.f07381ec.sfr@canb.auug.org.au>
On Tuesday 15 September 2009 08:53:09 Stephen Rothwell wrote:
> Hi Jens,
>
> On Tue, 15 Sep 2009 08:23:06 +0200 Jens Axboe <jens.axboe@oracle.com> wrote:
> > Fix looks correct.
>
> Thanks for the confirmation. So hopefully one of these trees will be
> merged by Linus soon an this can be fixed up in the other.
Thanks everybody.
I have applied Stephens' patch to the DRBD tree.
-phil
WARNING: multiple messages have this Message-ID (diff)
From: Philipp Reisner <philipp.reisner-63ez5xqkn6DQT0dZR+AlfA@public.gmane.org>
To: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
Cc: Nikanth Karthikesan <knikanth-l3A5Bk7waGM@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
drbd-dev-cunTk1MwBs8qoQakbn7OcQ@public.gmane.org,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Jens Axboe <jens.axboe-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Subject: Re: linux-next: drbd tree build failure
Date: Tue, 15 Sep 2009 16:03:23 +0200 [thread overview]
Message-ID: <200909151603.24843.philipp.reisner@linbit.com> (raw)
In-Reply-To: <20090915165309.f07381ec.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
On Tuesday 15 September 2009 08:53:09 Stephen Rothwell wrote:
> Hi Jens,
>
> On Tue, 15 Sep 2009 08:23:06 +0200 Jens Axboe <jens.axboe-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> wrote:
> > Fix looks correct.
>
> Thanks for the confirmation. So hopefully one of these trees will be
> merged by Linus soon an this can be fixed up in the other.
Thanks everybody.
I have applied Stephens' patch to the DRBD tree.
-phil
next prev parent reply other threads:[~2009-09-15 14:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 6:07 linux-next: drbd tree build failure Stephen Rothwell
2009-09-15 6:07 ` Stephen Rothwell
2009-09-15 6:23 ` Jens Axboe
2009-09-15 6:53 ` Stephen Rothwell
2009-09-15 6:57 ` Jens Axboe
2009-09-15 6:57 ` Jens Axboe
2009-09-15 7:45 ` Stephen Rothwell
2009-09-15 14:03 ` Philipp Reisner [this message]
2009-09-15 14:03 ` Philipp Reisner
-- strict thread matches above, loose matches on Subject: below --
2009-07-29 5:29 Stephen Rothwell
2009-07-29 5:47 ` Martin K. Petersen
2009-07-29 6:17 ` Stephen Rothwell
2009-08-18 5:32 ` Stephen Rothwell
2009-08-18 6:01 ` Martin K. Petersen
2009-07-29 5:29 Stephen Rothwell
2009-07-29 6:20 ` Jens Axboe
2009-07-29 15:13 ` Philipp Reisner
2009-07-27 7:37 Stephen Rothwell
2009-07-27 9:09 ` Philipp Reisner
2009-07-27 11:38 ` Alexander Beregalov
2009-07-27 15:07 ` Philipp Reisner
2009-07-28 4:19 ` Stephen Rothwell
2009-07-28 4:20 ` Stephen Rothwell
2009-07-27 5:48 Stephen Rothwell
2009-07-27 8:09 ` Lars Ellenberg
2009-07-27 17:17 ` Philipp Reisner
2009-07-28 4:20 ` Stephen Rothwell
2009-07-29 1:40 ` Rusty Russell
2009-07-29 15:11 ` Philipp Reisner
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=200909151603.24843.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=drbd-dev@lists.linbit.com \
--cc=jens.axboe@oracle.com \
--cc=knikanth@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.