From: Greg KH <greg@kroah.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>,
linux-media@vger.kernel.org,
Maxim Levitsky <maximlevitsky@gmail.com>,
Christoph Bartelmus <lirc@bartelmus.de>
Subject: Re: [PATCH 1/2] staging/lirc: port lirc_streamzap to ir-core
Date: Mon, 2 Aug 2010 18:00:20 -0700 [thread overview]
Message-ID: <20100803010020.GA3677@kroah.com> (raw)
In-Reply-To: <4C5761AE.9050701@redhat.com>
On Mon, Aug 02, 2010 at 09:24:14PM -0300, Mauro Carvalho Chehab wrote:
> Em 02-08-2010 19:35, Greg KH escreveu:
> > On Mon, Aug 02, 2010 at 05:29:22PM -0400, Jarod Wilson wrote:
> >> drivers/media/IR/keymaps/Makefile | 1 +
> >
> > Uppercase "IR"? Any reason why you all picked that?
>
> Infra Red. Well, it were not probably a good idea ;)
>
> Anyway, I intend to rename it to "rc" (for Remote Controller), change lots of
> internal structures and eventually move it to drivers/ or drivers/input, as the
> idea is to use the subsystem also to other kinds of remote controllers.
>
> I'll likely do it after finishing the merge of the pending patches, and send
> upstream during this merge window. It seems better to rename during the merge
> window.
Renames are usually good for after -rc1 is out to help everyone sync up
better.
thanks,
greg k-h
> >
> > Just curious.
> >
> > greg k-h
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-media" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> Cheers,
> Mauro
prev parent reply other threads:[~2010-08-03 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 21:29 [PATCH 1/2] staging/lirc: port lirc_streamzap to ir-core Jarod Wilson
2010-08-02 21:31 ` [PATCH 2/2] IR: put newly ported streamzap driver in proper home Jarod Wilson
2010-08-02 22:35 ` [PATCH 1/2] staging/lirc: port lirc_streamzap to ir-core Greg KH
2010-08-03 0:24 ` Mauro Carvalho Chehab
2010-08-03 1:00 ` 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=20100803010020.GA3677@kroah.com \
--to=greg@kroah.com \
--cc=jarod@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=lirc@bartelmus.de \
--cc=maximlevitsky@gmail.com \
--cc=mchehab@redhat.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