public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Jarkko Nikula <jhnikula@gmail.com>,
	Jonathan McDowell <noodles@earth.li>,
	Peter Ujfalusi <peter.ujfalusi@nokia.com>,
	Tony Lindgren <tony@atomide.com>,
	alsa-devel@alsa-project.org,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	e3-hacking@earth.li, Arun KS <arunks@mistralsolutions.com>
Subject: Re: [RFC] [PATCH 3/3 v2] ASoC: add support for Amstrad E3 (Delta) machine
Date: Fri, 31 Jul 2009 15:27:13 +0200	[thread overview]
Message-ID: <4A72F131.7010806@tis.icnet.pl> (raw)
In-Reply-To: <20090731131647.012afb23@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>>> Furthermore, I am still thinking about renaming the ldisc with a more 
>>> generic name. That way, it could be probably reused by other similiar 
>>> implementations. As long as the ldisc is registered from a board 
>>> specific code, it should not interfere with other implemnetations 
>>> reusing the same ldisc number, even if compiled in side by side.
>> Any objections on renaming ldisc from N_AMSDLETA to N_V253?
> 
> None
> 

Thanks, will resubmit as patch 2/3 v2 and 3/3 v3 then.

Janusz

      reply	other threads:[~2009-07-31 13:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 11:18 [RFC] [PATCH 3/3 v2] ASoC: add support for Amstrad E3 (Delta) machine Janusz Krzysztofik
2009-07-30  9:12 ` Janusz Krzysztofik
2009-07-31 21:38   ` Mark Brown
2009-07-31  9:52 ` Mark Brown
2009-07-31 11:58   ` Janusz Krzysztofik
2009-07-31 12:16     ` Alan Cox
2009-07-31 13:27       ` Janusz Krzysztofik [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=4A72F131.7010806@tis.icnet.pl \
    --to=jkrzyszt@tis.icnet.pl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=arunks@mistralsolutions.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=e3-hacking@earth.li \
    --cc=jhnikula@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=noodles@earth.li \
    --cc=peter.ujfalusi@nokia.com \
    --cc=tony@atomide.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