public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Allyn <mark.a.allyn@intel.com>,
	linux-kernel@vger.kernel.org, alan@linux.intel.com,
	charles.f.johnson@intel.com
Subject: Re: [PATCH] Rename rar_driver to rar_register
Date: Mon, 18 Jan 2010 20:06:41 -0800	[thread overview]
Message-ID: <20100119040641.GA9527@kroah.com> (raw)
In-Reply-To: <20100119012307.6b40d2db@lxorguk.ukuu.org.uk>

On Tue, Jan 19, 2010 at 01:23:07AM +0000, Alan Cox wrote:
> On Mon, 18 Jan 2010 16:12:43 -0800
> Greg KH <greg@kroah.com> wrote:
> 
> > On Mon, Jan 18, 2010 at 01:21:36PM -0800, Mark Allyn wrote:
> > > The purpose of this patch is to change the name of rar_register source
> > > files (both the .c and .h files) to rar_register.
> > > 
> > > This is the first of seven patches for the rar_register driver
> > > for Sunday, January 17, 2009
> > > 
> > > This is to clarify that this driver is for the rar_register.
> > 
> > What does that mean?  Why does the name matter?
> 
> RAR are the registers. The code handles the registers. There are things
> that use the registers which are drivers but are not this code. It could
> almost be "librar" except it's not quite used as a library

Ok, thanks for the info, it would be good to have this in the changelog
entry for the next patch series submission.

thanks,

greg k-h

      reply	other threads:[~2010-01-19  4:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 21:21 [PATCH] Rename rar_driver to rar_register Mark Allyn
2010-01-18 21:45 ` Marcel Holtmann
2010-01-19  0:12   ` Greg KH
2010-01-19  0:12 ` Greg KH
2010-01-19  1:23   ` Alan Cox
2010-01-19  4:06     ` Greg KH [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=20100119040641.GA9527@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@linux.intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=charles.f.johnson@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.a.allyn@intel.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