From: Jens Axboe <jens.axboe@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
mike.miller@hp.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 6/6] cciss: fix bug if scsi tape support is disabled
Date: Wed, 6 Aug 2008 12:33:08 +0200 [thread overview]
Message-ID: <20080806103308.GM20055@kernel.dk> (raw)
In-Reply-To: <20080806130825.1567d882.sfr@canb.auug.org.au>
On Wed, Aug 06 2008, Stephen Rothwell wrote:
> On Tue, 5 Aug 2008 15:30:12 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > I'm not seeing these changes in linux-next nor in
> > master.kernel.org/pub/scm/linux/kernel/git/axboe/linux-2.6-block.git#for-next
> > nor in #for-akpm.
>
> Well linux-next gets its block tree from
> git://git.kernel.dk/linux-2.6-block.git#for-next (which appears to be
> very similar - if not identical to - the above).
>
> > Also, #for-next is empty, but #for-akpm has the single commit
>
> The for-linus branch seems to have a few commits, though ...
> Jens, would you like that in linux-next as block-current (merged early -
> meant for bug fixes destined for the current release)?
Thanks, but just keep pulling linux-next and I'll try and get them
uptodate more frequently :-)
--
Jens Axboe
next prev parent reply other threads:[~2008-08-06 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 21:18 [PATCH 6/6] cciss: fix bug if scsi tape support is disabled Mike Miller
2008-08-04 9:56 ` Jens Axboe
2008-08-05 22:30 ` Andrew Morton
2008-08-06 3:08 ` Stephen Rothwell
2008-08-06 10:33 ` Jens Axboe [this message]
2008-08-06 23:43 ` Stephen Rothwell
2008-08-07 15:29 ` Miller, Mike (OS Dev)
2008-08-07 17:20 ` Jens Axboe
2008-08-07 18:25 ` Miller, Mike (OS Dev)
2008-08-07 18:28 ` Jens Axboe
2008-08-06 10:32 ` 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=20080806103308.GM20055@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mike.miller@hp.com \
--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.