From: "Williams, Dan J" <dan.j.williams@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the isci tree
Date: Fri, 23 Mar 2012 10:08:32 -0700 [thread overview]
Message-ID: <CABE8wwtBLGezYYi65_ZkrCZbt2f_t3LmvyCv3QLDGtTg4c3sJA@mail.gmail.com> (raw)
In-Reply-To: <20120323132646.9e258a9cf41be00e8a839065@canb.auug.org.au>
On Thu, Mar 22, 2012 at 7:26 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Dan,
>
> After merging the isci tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> drivers/scsi/ipr.c: In function 'ipr_ata_slave_alloc':
> drivers/scsi/ipr.c:4552:28: error: 'ap' undeclared (first use in this function)
>
> Caused by commit 837f52ee7a86 ("libsas, libata: fix start of life for a
> sas ata_port").
>
> I have used the isci tree from next-20120322 for today.
/me kicks himself for overlooking CONFIG_IPR=n in his .config
Fixed up and pushed out.
--
Dan
prev parent reply other threads:[~2012-03-23 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 2:26 linux-next: build failure after merge of the isci tree Stephen Rothwell
2012-03-23 17:08 ` Williams, Dan J [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=CABE8wwtBLGezYYi65_ZkrCZbt2f_t3LmvyCv3QLDGtTg4c3sJA@mail.gmail.com \
--to=dan.j.williams@intel.com \
--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 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).