From: Alexander Clouter <alex@digriz.org.uk>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for March 20 - timeriomem build break on s390
Date: Sat, 21 Mar 2009 10:38:17 +0000 [thread overview]
Message-ID: <20090321103817.GL22563@woodchuck> (raw)
In-Reply-To: <20090321061922.GA13990@gondor.apana.org.au>
Hi,
* Herbert Xu <herbert@gondor.apana.org.au> [2009-03-21 14:19:22+0800]:
>
> On Fri, Mar 20, 2009 at 10:09:01AM +0100, Heiko Carstens wrote:
> > 'hwrng: timeriomem' breaks an allyesconfig build on s390:
> >
> > CC drivers/char/hw_random/timeriomem-rng.o
> > drivers/char/hw_random/timeriomem-rng.c: In function 'timeriomem_rng_data_read':
> > drivers/char/hw_random/timeriomem-rng.c:60: error: implicit declaration of function 'readl'
> >
> > Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
>
> Patch applied. Thanks Heiko!
>
Yes, thanks for catching this.
Cheers
--
Alexander Clouter
.sigmonster says: Don't kiss an elephant on the lips today.
next prev parent reply other threads:[~2009-03-21 10:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 5:28 linux-next: Tree for March 20 Stephen Rothwell
2009-03-20 9:05 ` Next March 20 : drivers/md/dm-exception-store build break Sachin Sant
2009-03-20 9:09 ` linux-next: Tree for March 20 - timeriomem build break on s390 Heiko Carstens
2009-03-21 6:19 ` Herbert Xu
2009-03-21 10:38 ` Alexander Clouter [this message]
2009-03-20 9:14 ` linux-next: Tree for March 20 - dnet " Heiko Carstens
2009-03-20 11:06 ` [PATCH] dnet: DNET should depend on HAS_IOMEM Ilya Yanok
2009-03-21 23:58 ` David Miller
2009-03-20 12:59 ` linux-next: Tree for March 20 - crypto crash on s390 Heiko Carstens
2009-03-21 6:26 ` Herbert Xu
2009-03-21 10:56 ` Heiko Carstens
2009-03-21 13:13 ` Herbert Xu
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=20090321103817.GL22563@woodchuck \
--to=alex@digriz.org.uk \
--cc=heiko.carstens@de.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=schwidefsky@de.ibm.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.