From: Paul Bolle <pebolle@tiscali.nl>
To: Scott Jiang <scott.jiang.linux@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Steven Miao <realmz6@gmail.com>,
adi-buildroot-devel@lists.sourceforge.net,
linux-next@vger.kernel.org
Subject: Re: bf609: CONFIG_SND_BF6XX_PCM?
Date: Mon, 12 Jan 2015 11:08:33 +0100 [thread overview]
Message-ID: <1421057313.22660.22.camel@x220> (raw)
In-Reply-To: <1409400293.21896.78.camel@x220>
Hi Scott,
[Added Stephen Rothwell and linux-next.]
On Sat, 2014-08-30 at 14:04 +0200, Paul Bolle wrote:
> On Fri, 2014-08-22 at 17:13 +0800, Scott Jiang wrote:
> > 2014-08-18 17:53 GMT+08:00 Paul Bolle <pebolle@tiscali.nl>:
> > > Your commit 1e3bc3e86be6 ("bf609: use new SND_BF6XX_PCM to choose audio
> > > pcm driver") landed in today's linux-next (ie, next-20140818).
> > >
> > > It adds two checks for CONFIG_SND_BF6XX_PCM. There's currently no
> > > Kconfig symbol SND_BF6XX_PCM in linux-next. I assume the code to add
> > > that symbol is queued somewhere. Is that correct?
> > >
> > I plan to merge tdm driver into bf6xx pcm driver and send patches to
> > Mark Brown next week. Also this patch in arch/blackfin will be
> > included. Is it ok?
>
> I'm fine with about any way you'd like to resolve this. But if this
> hasn't changed in, say, a few months, I might send you a reminder.
These two checks can still be found in next-20150112. Since there's no
Kconfig symbol SND_BF6XX_PCM they will both evaluate to false. So this
is a reminder for this issue.
Are you still planning on adding that Kconfig symbol or should these two
checks (and the code they hide in linux-next) be removed?
Paul Bolle
parent reply other threads:[~2015-01-12 10:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1409400293.21896.78.camel@x220>]
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=1421057313.22660.22.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=linux-next@vger.kernel.org \
--cc=realmz6@gmail.com \
--cc=scott.jiang.linux@gmail.com \
--cc=sfr@canb.auug.org.au \
/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).