The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: jengelh@computergmbh.de, a.zummo@towertech.it,
	linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com
Subject: Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware
Date: Fri, 17 Aug 2007 09:26:44 -0700	[thread overview]
Message-ID: <200708170926.45194.david-b@pacbell.net> (raw)
In-Reply-To: <20070818.011501.41012303.anemo@mba.ocn.ne.jp>

On Friday 17 August 2007, Atsushi Nemoto wrote:
> 
> > My preferred style for such patches puts the MODULE_ALIAS up
> > near the strange driver name, so it's more clear what's going
> > on.  Putting all the MODULE_*() stuff at the end of the file
> > gets confusing in this case.
> 
> OK, then I should update my patches anyway ;)

I wasn't going to be too picky here, but if you volunteer
to make things even better, I'll be happy!  :)


> Which do you prefer, MODULE_ALIAS or change some strings?
> 
> I guess there are some out-of-tree users of this driver, but fixing
> them is really trivial, so I don't think this is a big compatibility
> problem.

If you're willing to fix all the in-tree users, I'd think
not needing MODULE_ALIAS is best in the long term.

For these I2C drivers, the conversion to support "new style"
driver binding is new in 2.6.23, yes?  If so, I don't see any
real downside to making the driver and module names match.

_ Dave


  reply	other threads:[~2007-08-17 16:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 16:06 [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware Atsushi Nemoto
2007-08-17 10:59 ` Jan Engelhardt
2007-08-17 15:23   ` David Brownell
2007-08-17 15:37     ` Jan Engelhardt
2007-08-17 16:02       ` David Brownell
2007-08-17 16:15         ` Atsushi Nemoto
2007-08-17 16:26           ` David Brownell [this message]
2007-08-17 16:32           ` Kay Sievers
2007-08-17 16:55             ` David Brownell
2007-08-17 17:18               ` Kay Sievers
2007-08-17 19:50                 ` David Brownell
2007-08-17 19:52                   ` Jan Engelhardt
2007-08-17 20:20                     ` David Brownell
2007-08-18  2:40                   ` Kay Sievers
2007-08-18  4:06                     ` David Brownell
2007-08-18 10:45                       ` Kay Sievers
2007-08-20  1:44                         ` legacy platform drivers and hotplugging David Brownell
2007-08-20  2:02                           ` Atsushi Nemoto
2007-08-20  9:51                           ` Kay Sievers
2007-08-19 12:57             ` [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware Atsushi Nemoto
2007-08-19 21:45               ` Kay Sievers
2007-08-20  1:48                 ` David Brownell
2007-08-20  2:02                   ` David Brownell
2007-08-20  2:16                     ` Atsushi Nemoto
2007-08-17 16:04       ` Atsushi Nemoto

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=200708170926.45194.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=a.zummo@towertech.it \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox