From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-next@vger.kernel.org, "Alfred E. Heggestad" <aeh@db.org>
Subject: Re: linux-next: input tree build failure
Date: Tue, 19 Aug 2008 13:00:57 -0700 [thread overview]
Message-ID: <20080819200057.GD10502@kroah.com> (raw)
In-Reply-To: <20080819163148.159c7d8c.sfr@canb.auug.org.au>
On Tue, Aug 19, 2008 at 04:31:48PM +1000, Stephen Rothwell wrote:
> Hi Dmitry,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> drivers/input/misc/cm109.c: In function 'cm109_usb_suspend':
> drivers/input/misc/cm109.c:768: error: implicit declaration of function 'info'
>
> Caused by commit c04148f915e5ba7947752e6348e0da4cdab1329e ("Input: add
> driver for USB VoIP phones with CM109 chipset") adding a usage of the info
> () function while commit 8aac48f4f2460b00468fd5f1101addf3df04e94c ("USB:
> remove info() macro from usb.h") from the usb tree removed it.
>
> I applied the following patch (which may not be the best).
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
>
> >From 2a58297038a91ef5ffba3df4a5bd7576735ca205 Mon Sep 17 00:00:00 2001
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 19 Aug 2008 16:28:15 +1000
> Subject: [PATCH] input/cm109: fix up for info() removal
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> drivers/input/misc/cm109.c | 26 +++++++++++++++++---------
> 1 files changed, 17 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/input/misc/cm109.c b/drivers/input/misc/cm109.c
> index 404fd49..595b3b1 100644
> --- a/drivers/input/misc/cm109.c
> +++ b/drivers/input/misc/cm109.c
> @@ -312,7 +312,8 @@ static void cm109_urb_irq_callback(struct urb *urb)
> int error;
>
> #if CM109_DEBUG
> - info("### URB IRQ: [0x%02x 0x%02x 0x%02x 0x%02x] keybit=0x%02x",
> + printk(KERN_INFO KBUILD_MODNAME ": "
> + "### URB IRQ: [0x%02x 0x%02x 0x%02x 0x%02x] keybit=0x%02x",
No, these should all use dev_info() instead.
Actually, they should all use dev_dbg() and drop the #if entirely. With
the dynamic dev_dbg() patch that is in -next, that will work just fine,
no need to rebuild modules which is almost impossible for most users to
do.
thanks,
greg k-h
next prev parent reply other threads:[~2008-08-19 20:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 6:31 linux-next: input tree build failure Stephen Rothwell
2008-08-19 13:01 ` Dmitry Torokhov
2008-08-19 19:59 ` Greg KH
2008-08-19 20:00 ` Greg KH [this message]
2008-08-20 5:49 ` Stephen Rothwell
2008-08-20 18:35 ` Greg KH
2008-08-22 20:29 ` Dmitry Torokhov
2008-08-22 22:15 ` Alfred E. Heggestad
2008-08-25 0:01 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-03-10 4:49 Stephen Rothwell
2009-03-10 5:02 ` Dmitry Torokhov
2009-03-10 5:14 ` Stephen Rothwell
2009-12-07 9:03 Stephen Rothwell
2009-12-07 16:25 ` Randy Dunlap
2009-12-07 17:36 ` Dmitry Torokhov
2009-12-07 22:16 ` Stephen Rothwell
2010-01-25 5:52 Stephen Rothwell
2010-01-25 6:46 ` Dmitry Torokhov
2010-01-25 7:26 ` Tobias Klauser
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=20080819200057.GD10502@kroah.com \
--to=greg@kroah.com \
--cc=aeh@db.org \
--cc=dmitry.torokhov@gmail.com \
--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 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.