From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jens Axboe <jens.axboe@oracle•com>
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: Sat, 18 Oct 2008 00:15:33 +1100 [thread overview]
Message-ID: <20081018001533.06ec0d1b.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20081017105753.GG19428@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
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).
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-17 13:15 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 [this message]
2008-10-17 13:37 ` Jens Axboe
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=20081018001533.06ec0d1b.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jens.axboe@oracle$(echo .)com \
--cc=kamalesh@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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