From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: David Miller <davem@davemloft.net>
Cc: tedheadster@gmail.com, netdev@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] eisa: standardize on eisa_register_driver like similar bus registrations
Date: Tue, 08 Oct 2013 08:53:18 +0400 [thread overview]
Message-ID: <1381207998.7959.1.camel@dabdike> (raw)
In-Reply-To: <20131007.160225.1679994399484815968.davem@davemloft.net>
On Mon, 2013-10-07 at 16:02 -0400, David Miller wrote:
> From: Matthew Whitehead <tedheadster@gmail.com>
> Date: Sat, 5 Oct 2013 22:35:58 -0400
>
> > The other buses (isa, pci, pnp, parport, usb, tty, etc) all use the convention
> > of ${BUSNAME}_register_driver. Rewrite the little remaining code that uses EISA
> > to follow this convention for easier readability.
> >
> > This affects the EISA bus, SCSI, and networking subsystems so only one should
> > ultimately merge the patch if it is accepted.
> >
> > Signed-off-by: Matthew Whitehead <tedheadster@gmail.com>
>
> I'm fine with someone else taking this, for networking parts:
I don't really see much value in the rename, especially as eisa is
probably not long for this world. However, its a trivial rename, so
bundle it all up into a single patch and send it to Jiří Kosina
<trivial@vger.kernel.org> he'll take care of it.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-10-08 4:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 2:35 [PATCH] eisa: standardize on eisa_register_driver like similar bus registrations Matthew Whitehead
2013-10-07 20:02 ` David Miller
2013-10-08 4:53 ` James Bottomley [this message]
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=1381207998.7959.1.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=davem@davemloft.net \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tedheadster@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).