From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Jens Axboe <jens.axboe@oracle.com>,
linux-next@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: linux-next: scsi build breakage
Date: Wed, 19 Mar 2008 10:01:44 -0500 [thread overview]
Message-ID: <1205938904.11527.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20080319180528.0ebcabe7.sfr@canb.auug.org.au>
On Wed, 2008-03-19 at 18:05 +1100, Stephen Rothwell wrote:
> I need the following patch to make various powerpc configs build.
> sg_copy_buffer is introduced by commit
> d9c3ddd20a2a1fca9655937d4fc636fcb8e9f59e ("[SCSI] block: add sg buffer
> copy helper functions") in the scsi/master branch included into
> yesterday's (and today's) linux-next tree.
>
> I have applied this patch to today's linux-next tree.
Tomo already redid his tree with a fix for this yesterday ... since it
involves unwinding and redoing 10 patches, I'm just being lazy.
James
prev parent reply other threads:[~2008-03-19 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 7:05 linux-next: scsi build breakage Stephen Rothwell
2008-03-19 15:01 ` James Bottomley [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=1205938904.11527.5.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--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