All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Derek [方德義]" <derek.fang@realtek.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Oder Chiou" <oder_chiou@realtek.com>,
	"Jack Yu" <jack.yu@realtek.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"Albert Chen" <albertchen@realtek.com>,
	"bard.liao@intel.com" <bard.liao@intel.com>,
	"Shuming [范書銘]" <shumingf@realtek.com>,
	"Flove(HsinFu)" <flove@realtek.com>
Subject: Re: [PATCH] ASoC: rt1308: Add RT1308 amplifier driver
Date: Thu, 16 May 2019 13:46:53 +0000	[thread overview]
Message-ID: <BC6F7617C38F3E4E8CA887E07B35B82805B15635@RTITMBSVM07.realtek.com.tw> (raw)
In-Reply-To: <20190515161429.GH5613@sirena.org.uk>

> Subject: Re: [PATCH] ASoC: rt1308: Add RT1308 amplifier driver
> 
> On Tue, May 14, 2019 at 11:10:58AM +0000, Derek [方德義] wrote:
> 
> > I could remove comment for the limit setting in register patch/init list
> > to avoid users or integrators have any expectation.
> > And also there will not be any support at all the driver according to the
> > limit setting.
> 
> It's better to have a comment than not have one, I think I'd be happier
> if I understood what was actually being limited here - that might make
> it clear why it's not system specific which is what's concerning me.

I will give a comment that describes the limit setting reason clearly.

> ------Please consider the environment before printing this e-mail.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2019-05-16 13:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16  2:22 [PATCH] ASoC: rt1308: Add RT1308 amplifier driver derek.fang
     [not found] ` <20190416153510.GE4834@sirena.org.uk>
     [not found]   ` <BC6F7617C38F3E4E8CA887E07B35B8280116192E@RTITMBSVM07.realtek.com.tw>
2019-04-17 15:05     ` Mark Brown
2019-04-23 13:39       ` Derek [方德義]
2019-05-08  6:45         ` Mark Brown
2019-05-08 13:17           ` Derek [方德義]
2019-05-12  8:06             ` Mark Brown
2019-05-13 13:54               ` Derek [方德義]
2019-05-13 14:56                 ` Mark Brown
2019-05-14 11:10                   ` Derek [方德義]
2019-05-15 16:14                     ` Mark Brown
2019-05-16 13:46                       ` Derek [方德義] [this message]
2019-05-16 16:52                         ` Mark Brown
2019-04-17 12:05 derek.fang

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=BC6F7617C38F3E4E8CA887E07B35B82805B15635@RTITMBSVM07.realtek.com.tw \
    --to=derek.fang@realtek.com \
    --cc=albertchen@realtek.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bard.liao@intel.com \
    --cc=broonie@kernel.org \
    --cc=flove@realtek.com \
    --cc=jack.yu@realtek.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.com \
    --cc=shumingf@realtek.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.