From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 1/1 - try2] ASoC: add support for multiple cards/codecs in debugfs
Date: Thu, 1 Oct 2009 12:09:19 +0100 [thread overview]
Message-ID: <20091001110919.GC19998@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <200910011402.04406.peter.ujfalusi@nokia.com>
On Thu, Oct 01, 2009 at 02:02:04PM +0300, Peter Ujfalusi wrote:
> On Thursday 01 October 2009 13:51:07 ext Mark Brown wrote:
> > I'd rather use dev_name() for the CODEC itself if possible, that is more
> > likely to be stable going forward and one of the immediate aims with the
> > API refactoring is to remove socdev entirely at runtime.
> At this point the codec->dev was NULL, that is why I have used the socdev->dev
> instead.
Right, your CODEC driver needs updating to current APIs. Omitting the
device name is a good fallback here since you won't be able to have more
than one of the same device anyway if a device isn't provided.
> > > ret = snd_pcm_hw_constraint_minmax(substream->runtime,
> > but this doesn't seem to accomplish that goal? I can't actually spot
> > the difference either, I'm assuming it's just whitespace? If so I'll
> > apply as-is.
> It is my editor, which removed the tailing space from that line, I have
> mentioned it in the intro mail.
Oh, right. Like I was saying yesterday it's better to not use a
separate cover letter for single patches.
next prev parent reply other threads:[~2009-10-01 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 7:32 [PATCH 0/1 - try2] ASoC: debugfs support improvement Peter Ujfalusi
2009-10-01 7:32 ` [PATCH 1/1 - try2] ASoC: add support for multiple cards/codecs in debugfs Peter Ujfalusi
2009-10-01 10:51 ` Mark Brown
2009-10-01 11:02 ` Peter Ujfalusi
2009-10-01 11:09 ` Mark Brown [this message]
2009-10-01 13:49 ` Peter Ujfalusi
2009-10-01 14:06 ` Mark Brown
2009-10-01 11:19 ` Mark Brown
2009-10-01 13:06 ` Peter Ujfalusi
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=20091001110919.GC19998@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=peter.ujfalusi@nokia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.