From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jean Delvare <khali@linux-fr.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (jdelvare-hwmon tree related)
Date: Tue, 15 Mar 2011 21:22:26 +1100 [thread overview]
Message-ID: <20110315212226.7e940b51.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20110315103228.30233acc@endymion.delvare>
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
Hi Jean,
On Tue, 15 Mar 2011 10:32:28 +0100 Jean Delvare <khali@linux-fr.org> wrote:
>
> Stephen, sorry for the inconvenience, both Hans and myself build-tested
> the new code on an architecture where <linux/delay.h> gets included
> implicitly, so we didn't notice it was missing.
It happens. It seems that delay.h is almost always the one that is
forgotten. X86 builds include it implicitly but powerpc doesn't.
I wonder if we could concoct a nice checkpatch test for it.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-03-15 10:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 8:24 linux-next: build failure after merge of the final tree (jdelvare-hwmon tree related) Stephen Rothwell
2011-03-15 8:40 ` Hans de Goede
2011-03-15 9:32 ` Jean Delvare
2011-03-15 10:22 ` Stephen Rothwell [this message]
2011-03-16 11:30 ` Jean Delvare
2011-03-17 12:18 ` Geert Uytterhoeven
2011-03-17 15:36 ` Jean Delvare
2011-03-16 16:16 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2010-10-06 4:28 Stephen Rothwell
2010-10-06 7:05 ` Jean Delvare
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=20110315212226.7e940b51.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hdegoede@redhat.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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