[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1244218042.3631.158.camel@Joe-Laptop.home>
Date: Fri, 05 Jun 2009 09:07:22 -0700
From: Joe Perches <joe@...ches.com>
To: Corentin Chary <corentin.chary@...il.com>
Cc: Alan Jenkins <alan-jenkins@...fmail.co.uk>,
acpi4asus-user@...ts.sourceforge.net,
LKML <linux-kernel@...r.kernel.org>,
Len Brown <len.brown@...el.com>,
Matthew Garrett <mjg@...hat.com>,
Darren Salt <linux@...mustbejoking.demon.co.uk>
Subject: Re: [PATCH] eeepc-laptop.c: use pr_fmt and pr_<level>
On Fri, 2009-06-05 at 18:01 +0200, Corentin Chary wrote:
> On Fri, Jun 5, 2009 at 5:45 PM, Joe Perches<joe@...ches.com> wrote:
> > On Fri, 2009-06-05 at 13:57 +0200, Corentin Chary wrote:
> >> On Fri, Jun 5, 2009 at 1:00 PM, Joe Perches<joe@...ches.com> wrote:
> >> > On Fri, 2009-06-05 at 11:54 +0100, Alan Jenkins wrote:
> >> >> Is EEEPC_HOTK_FILE used anywhere else? It would be clearer if you were
> >> >> able to just use "eeepc: " or whatever and remove the definition of
> >> >> EEEPC_HOTK_FILE.
> >> > It is used elsewhere and perhaps it'd be better to use KBUILD_MODNAME.
> >> I think we can't use KBUILD_MODNAME because "eeepc" is used for
> >> platform_device, backlight and input device. Using "eeepc-laptop"
> >> would break compatibility.
> > What compatibility would it break?
> > Logging messages are not guaranteed to be stable across versions.
> for platform_device backlight and input device it would change the
> "/sys" paths (eg: /sys/class/backlight/eeepc)
I see what you mean. We're talking cross purposes though.
I meant that KBUILD_MODNAME be used for pr_fmt, not anywhere else.
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
So, no changes to any other EEPC_HOTK_FILE uses.
cheers, Joe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists