From: Jens Axboe <jens.axboe@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: [BUG] linux-next: Tree for October 16 - softlockup detected at blk_invoke_request_fn
Date: Fri, 17 Oct 2008 15:37:50 +0200 [thread overview]
Message-ID: <20081017133750.GL19428@kernel.dk> (raw)
In-Reply-To: <20081018001533.06ec0d1b.sfr@canb.auug.org.au>
On Sat, Oct 18 2008, Stephen Rothwell wrote:
> Hi Jens,
>
> On Fri, 17 Oct 2008 12:57:55 +0200 Jens Axboe <jens.axboe@oracle.com> wrote:
> >
> > OK, I'm guessing it's a merge mess in linux-next. I tried to look at the
> > diff, but it was pretty much impossible to read and even included lots
> > of things in -git already.
>
> If you are looking at the linux-next patch on kernel.org, then it is
> relative to 2.6.27, so will contain a lot of stuff in Linus' tree. Its
> purpose is to allow people to recreate the linux-next tree from a kernel
> tarball.
>
> In the linux-next git tree, the point in Linus' tree that it is based on
> the the "stable" branch. If necessary, people should be able to bisect
> between the "stabel" and "master" branches of a linux-next tree. Or, I
> am told, between one linux-next tree and another (but that sounds painful
> to me).
OK, I'll try the -git tree next time I have to lookup changes in -next.
Thanks for the explanation!
--
Jens Axboe
prev parent reply other threads:[~2008-10-17 13:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 10:18 linux-next: Tree for October 16 Stephen Rothwell
2008-10-16 10:40 ` Stephen Rothwell
[not found] ` <20081016211811.a523c8f2.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-10-16 13:47 ` Alexey Dobriyan
2008-10-16 18:41 ` Alexey Dobriyan
2008-10-16 22:22 ` David Howells
2008-10-16 19:23 ` [PATCH] linux-next: Tree for October 16 - build failure at MAL support on powerpc Kamalesh Babulal
2008-10-16 19:27 ` Josh Boyer
2008-10-16 19:58 ` Kamalesh Babulal
2008-10-16 20:42 ` [BUG] linux-next: Tree for October 16 - softlockup detected at blk_invoke_request_fn Kamalesh Babulal
2008-10-17 6:55 ` Jens Axboe
2008-10-17 10:24 ` Kamalesh Babulal
2008-10-17 10:57 ` Jens Axboe
2008-10-17 13:15 ` Stephen Rothwell
2008-10-17 13:37 ` 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=20081017133750.GL19428@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).