public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Linus <torvalds@linux-foundation•org>,
	Andrew Morton <akpm@linux-foundation•org>
Cc: 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>,
	Jarod Wilson <jarod@redhat•com>
Subject: linux-next: build failure after merge of the Linus' tree
Date: Fri, 25 Mar 2011 12:35:35 +1100	[thread overview]
Message-ID: <20110325123535.f980dfe8.sfr@canb.auug.org.au> (raw)

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

Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
 drivers/media/rc/ite-cir.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/media/rc/ite-cir.c b/drivers/media/rc/ite-cir.c
index 9be6a83..ac0e42b 100644
--- a/drivers/media/rc/ite-cir.c
+++ b/drivers/media/rc/ite-cir.c
@@ -187,7 +187,7 @@ static void ite_decode_bytes(struct ite_dev *dev, const u8 * data, int
 	sample_period = dev->params.sample_period;
 	ldata = (unsigned long *)data;
 	size = length << 3;
-	next_one = generic_find_next_le_bit(ldata, size, 0);
+	next_one = find_next_bit_le(ldata, size, 0);
 	if (next_one > 0) {
 		ev.pulse = true;
 		ev.duration =
@@ -196,14 +196,14 @@ static void ite_decode_bytes(struct ite_dev *dev, const u8 * data, int
 	}
 
 	while (next_one < size) {
-		next_zero = generic_find_next_zero_le_bit(ldata, size, next_one + 1);
+		next_zero = find_next_zero_bit_le(ldata, size, next_one + 1);
 		ev.pulse = false;
 		ev.duration = ITE_BITS_TO_NS(next_zero - next_one, sample_period);
 		ir_raw_event_store_with_filter(dev->rdev, &ev);
 
 		if (next_zero < size) {
 			next_one =
-			    generic_find_next_le_bit(ldata,
+			    find_next_bit_le(ldata,
 						     size,
 						     next_zero + 1);
 			ev.pulse = true;
-- 
1.7.4.1

             reply	other threads:[~2011-03-25  1:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25  1:35 Stephen Rothwell [this message]
2011-03-25 13:56 ` linux-next: build failure after merge of the Linus' tree Jarod Wilson
  -- strict thread matches above, loose matches on Subject: below --
2011-03-30  0:00 Stephen Rothwell
2011-03-30  1:56 ` Benjamin Herrenschmidt
2011-03-30  0:00 Stephen Rothwell
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=20110325123535.f980dfe8.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=akinobu.mita@gmail$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=jarod@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mchehab@redhat$(echo .)com \
    --cc=skandalfo@gmail$(echo .)com \
    --cc=torvalds@linux-foundation$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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