From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: linux-next: ide/sparc build failure
Date: Tue, 8 Jul 2008 19:48:32 +0200 [thread overview]
Message-ID: <200807081948.32605.bzolnier@gmail.com> (raw)
In-Reply-To: <20080708224803.8ce5aa56.sfr@canb.auug.org.au>
On Tuesday 08 July 2008, Stephen Rothwell wrote:
> Hi Bart,
>
> Today's linux-next build (sparc allmodconfig) failed like this:
>
> drivers/ide/setup-pci.c:203: error: `DMA_32BIT_MASK' undeclared (first use in this function)
> drivers/ide/setup-pci.c:203: error: (Each undeclared identifier is reported only once
> drivers/ide/setup-pci.c:203: error: for each function it appears in.)
>
> Caused by commit 711304186fe494bee4b9c94b3c195b167b2d4b87 ("ide: remove
> needless includes from setup-pci.c"). Seems like it was overdone.
indeed...
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
thanks, fixed in the guilty patch now
prev parent reply other threads:[~2008-07-08 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 12:48 linux-next: ide/sparc build failure Stephen Rothwell
2008-07-08 17:48 ` Bartlomiej Zolnierkiewicz [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=200807081948.32605.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--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).