From: Jarod Wilson <jarod@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Akinobu Mita <akinobu.mita@gmail.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
"Juan J. Garcia de Soria" <skandalfo@gmail.com>
Subject: Re: linux-next: build failure after merge of the Linus' tree
Date: Fri, 25 Mar 2011 09:56:09 -0400 [thread overview]
Message-ID: <20110325135609.GB28606@redhat.com> (raw)
In-Reply-To: <20110325123535.f980dfe8.sfr@canb.auug.org.au>
On Fri, Mar 25, 2011 at 12:35:35PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> In Linus' tree, today's linux-next build (x86_64 allmodconfig) failed
> like this:
>
> drivers/media/rc/ite-cir.c: In function 'ite_decode_bytes':
> drivers/media/rc/ite-cir.c:190: error: implicit declaration of function 'generic_find_next_le_bit'
> drivers/media/rc/ite-cir.c:199: error: implicit declaration of function 'generic_find_next_zero_le_bit'
>
> Caused by commit 620a32bba4a2 ("[media] rc: New rc-based ite-cir driver
> for several ITE CIRs") interacting with commit c4945b9ed472
> ("asm-generic: rename generic little-endian bitops functions").
>
> I applied the patch below for today.
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Fri, 25 Mar 2011 12:30:05 +1100
> Subject: [PATCH] [media] rc: update for bitop name changes
Thanks Stephen, obviously the correct thing to do here.
Acked-by: Jarod Wilson <jarod@redhat.com>
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2011-03-25 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 1:35 linux-next: build failure after merge of the Linus' tree Stephen Rothwell
2011-03-25 13:56 ` Jarod Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-30 0:00 Stephen Rothwell
2011-03-30 0:00 ` Stephen Rothwell
2011-03-30 1:56 ` Benjamin Herrenschmidt
2011-03-30 1:56 ` Benjamin Herrenschmidt
2011-03-30 0:00 Stephen Rothwell
2011-03-30 0:00 ` Stephen Rothwell
2011-03-30 1:57 ` Benjamin Herrenschmidt
2011-03-30 1:57 ` Benjamin Herrenschmidt
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=20110325135609.GB28606@redhat.com \
--to=jarod@redhat.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=skandalfo@gmail.com \
--cc=torvalds@linux-foundation.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 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.