From: Mark Brown <broonie@kernel.org>
To: Bhumika Goyal <bhumirks@gmail.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
Liam Girdwood <lgirdwood@gmail.com>,
perex@perex.cz, tiwai@suse.com, maxime.ripard@free-electrons.com,
Chen-Yu Tsai <wens@csie.org>,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
brian.austin@cirrus.com, Paul.Handrigan@cirrus.com,
support.opensource@diasemi.com,
Muthumula Jaya <mr.swami.reddy@ti.com>,
vishwas.a.deshpande@ti.com, peda@axentia.se,
bardliao@realtek.com, baohua@kernel.org, peter.ujfalusi@ti.com,
patches@opensource.cirrus.com
Subject: Re: [PATCH 1/2] ASoC: codecs: add const to snd_soc_codec_driver structures
Date: Thu, 10 Aug 2017 16:31:58 +0100 [thread overview]
Message-ID: <20170810153158.hfnzjzro7wnmc4mt@sirena.org.uk> (raw)
In-Reply-To: <CAOH+1jGe_Xo3o024H4xq8cJV10xta76QmovPKreXpncU86hqFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
On Thu, Aug 10, 2017 at 08:56:35PM +0530, Bhumika Goyal wrote:
> On Thu, Aug 10, 2017 at 8:50 PM, Mark Brown <broonie@kernel.org> wrote:
> > This is difficult to apply against current code as it is a single commit
> > over lots of files but the ASoC tree has lots of branches. I've figured
> > out the dependencies but it's easier to split things up (and avoids
> > collisions with other changes causing the whole thing to not apply).
> Thanks for the response.
> Should I make separate patches for each file or is there another way
> to split this patch?
Splitting per driver would've been easier, or saying exactly where it
applies if you don't split it. Like I say I figured it out for this one.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-08-10 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 16:00 [PATCH 0/2] ASoC: make snd_soc_codec_driver structures const Bhumika Goyal
2017-08-03 16:00 ` [PATCH 1/2] ASoC: codecs: add const to snd_soc_codec_driver structures Bhumika Goyal
2017-08-10 15:20 ` Mark Brown
2017-08-10 15:26 ` Bhumika Goyal
2017-08-10 15:31 ` Mark Brown [this message]
2017-08-10 15:42 ` Applied "ASoC: codecs: add const to snd_soc_codec_driver structures" to the asoc tree Mark Brown
2017-08-03 16:00 ` [PATCH 2/2] ASoC: sunxi: make snd_soc_codec_driver structures as const Bhumika Goyal
2017-08-07 11:52 ` Applied "ASoC: sunxi: make snd_soc_codec_driver structures as const" 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=20170810153158.hfnzjzro7wnmc4mt@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Paul.Handrigan@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=baohua@kernel.org \
--cc=bardliao@realtek.com \
--cc=bhumirks@gmail.com \
--cc=brian.austin@cirrus.com \
--cc=julia.lawall@lip6.fr \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mr.swami.reddy@ti.com \
--cc=patches@opensource.cirrus.com \
--cc=peda@axentia.se \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@ti.com \
--cc=support.opensource@diasemi.com \
--cc=tiwai@suse.com \
--cc=vishwas.a.deshpande@ti.com \
--cc=wens@csie.org \
/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).