From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Greg KH <greg@kroah.com>,
alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: Dynamically allocate the rtd device for a non-empty release
Date: Mon, 9 Jan 2012 21:14:18 +0000 [thread overview]
Message-ID: <20120109211418.GC30766@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5hd3atkwrj.wl%tiwai@suse.de>
On Mon, Jan 09, 2012 at 11:14:56AM +0100, Takashi Iwai wrote:
> Mark Brown wrote:
> > Greg, you asked for this to be included in 3.3 but I really don't see
> > any reason for doing so - this isn't exactly new code and there aren't
> > any practical issues being reported. Is there any actual rush?
> Since it's no urgent fix, rc1 is the best merge point. Of course, I
> know it's a bit too late for merge, but the code doesn't look so
> awfully intrusive. So, I find it's OK.
I'm still not thrilled by it but whatever.
prev parent reply other threads:[~2012-01-09 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 7:02 [PATCH] ASoC: Dynamically allocate the rtd device for a non-empty release Mark Brown
2012-01-09 10:14 ` Takashi Iwai
2012-01-09 21:14 ` Mark Brown [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=20120109211418.GC30766@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=greg@kroah.com \
--cc=lrg@ti.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=tiwai@suse.de \
/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).