From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Vinod Koul <vinod.koul@intel.com>,
Brian Austin <brian.austin@cirrus.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Paul Handrigan <Paul.Handrigan@cirrus.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH 3/7] ASoC: intel: bxt: Constify hw_constraints
Date: Tue, 13 Jun 2017 22:29:14 +0200 [thread overview]
Message-ID: <s5hwp8ftyw5.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170613202652.pt53jvmqkulorhc4@sirena.org.uk>
On Tue, 13 Jun 2017 22:26:52 +0200,
Mark Brown wrote:
>
> On Thu, Jun 08, 2017 at 11:37:21PM +0200, Takashi Iwai wrote:
> > snd_pcm_hw_constraint_list(), *_ratnums() and *_ratdens() receive the
> > const pointers. Constify the corresponding static objects for better
> > hardening.
>
> This doesn't apply against current code, please check and resend.
Or, you can send a pull request more often, instead of only once per
development cycle? :)
Don't worry, mine is a trivial one, will resend.
thanks,
Takashi
next prev parent reply other threads:[~2017-06-13 20:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 21:37 [PATCH 0/7] ASoC: Constify hw_constraints Takashi Iwai
2017-06-08 21:37 ` [PATCH 1/7] ASoC: cs35l34: " Takashi Iwai
2017-06-13 21:08 ` Applied "ASoC: cs35l34: Constify hw_constraints" to the asoc tree Mark Brown
2017-06-08 21:37 ` [PATCH 2/7] ASoC: cs53l30: Constify hw_constraints Takashi Iwai
2017-06-13 21:08 ` Applied "ASoC: cs53l30: Constify hw_constraints" to the asoc tree Mark Brown
2017-06-08 21:37 ` [PATCH 3/7] ASoC: intel: bxt: Constify hw_constraints Takashi Iwai
2017-06-13 20:26 ` Mark Brown
2017-06-13 20:29 ` Takashi Iwai [this message]
2017-06-08 21:37 ` [PATCH 4/7] ASoC: intel: byt: " Takashi Iwai
2017-06-09 3:36 ` Vinod Koul
2017-06-13 21:08 ` Applied "ASoC: intel: byt: Constify hw_constraints" to the asoc tree Mark Brown
2017-06-08 21:37 ` [PATCH 5/7] ASoC: intel: skl: Constify hw_constraints Takashi Iwai
2017-06-09 3:36 ` Vinod Koul
2017-06-13 21:08 ` Applied "ASoC: intel: skl: Constify hw_constraints" to the asoc tree Mark Brown
2017-06-08 21:37 ` [PATCH 6/7] ASoC: mediatek: Constify hw_constraints Takashi Iwai
2017-06-09 7:39 ` Matthias Brugger
2017-06-13 21:08 ` Applied "ASoC: mediatek: Constify hw_constraints" to the asoc tree Mark Brown
2017-06-08 21:37 ` [PATCH 7/7] ASoC: samsung: Constify hw_constraints Takashi Iwai
2017-06-09 7:09 ` Krzysztof Kozlowski
2017-06-13 21:08 ` Applied "ASoC: samsung: Constify hw_constraints" to the asoc tree Mark Brown
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=s5hwp8ftyw5.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Paul.Handrigan@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.com \
--cc=broonie@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=vinod.koul@intel.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.