All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hans J. Koch" <hjk@linutronix.de>
To: Greg KH <gregkh@suse.de>
Cc: Uwe Kleine-Koenig <Uwe.Kleine-Koenig@digi.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] UIO: Change driver name of uio_pdrv
Date: Tue, 8 Jul 2008 00:23:00 +0200	[thread overview]
Message-ID: <20080707222300.GA5149@local> (raw)

Hi Greg,
I'm just about to use the generic UIO platform device driver in a
project. I noticed the driver registers itself simply as "uio". We
should choose a more unique name here. The oneliner below goes on top of
the other UIO patches you've got in your queue right now. This is not in
mainline yet.

Thanks,
Hans

-------------------------

The generic UIO platform device driver should be given a unique driver ID and
not just "uio". This is especially important since Magnus Damm announced a
similar driver named uio_pdrv_genirq. We should get the names right before
this hits mainline.

Signed-off-by: Hans J. Koch <hjk@linutronix.de>
---
 drivers/uio/uio_pdrv.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux-2.6.26-rc/drivers/uio/uio_pdrv.c
===================================================================
--- linux-2.6.26-rc.orig/drivers/uio/uio_pdrv.c	2008-07-07 23:57:44.000000000 +0200
+++ linux-2.6.26-rc/drivers/uio/uio_pdrv.c	2008-07-07 23:58:26.000000000 +0200
@@ -12,7 +12,7 @@
 #include <linux/uio_driver.h>
 #include <linux/stringify.h>
 
-#define DRIVER_NAME "uio"
+#define DRIVER_NAME "uio_pdrv"
 
 struct uio_platdata {
 	struct uio_info *uioinfo;

             reply	other threads:[~2008-07-07 22:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07 22:23 Hans J. Koch [this message]
2008-07-08 10:48 ` [PATCH] UIO: Change driver name of uio_pdrv Uwe Kleine-König

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=20080707222300.GA5149@local \
    --to=hjk@linutronix.de \
    --cc=Uwe.Kleine-Koenig@digi.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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.