[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190124192652.GK5641@sirena.org.uk>
Date: Thu, 24 Jan 2019 19:26:52 +0000
From: Mark Brown <broonie@...nel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Cc: rohkumar@....qualcomm.com, alsa-devel@...a-project.org,
bgoswami@...eaurora.org, vinod.koul@...aro.org,
lgirdwood@...il.com, Curtis Malainey <cujomalainey@...gle.com>,
plai@...eaurora.org, linux-kernel@...r.kernel.org,
Ajit Pandey <ajitp@...eaurora.org>, tiwai@...e.com,
Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
Matthias Reichl <hias@...us.com>,
Rohit kumar <rohitkr@...eaurora.org>, asishb@...eaurora.org,
srinivas.kandagatla@...aro.org,
Curtis Malainey <cujomalainey@...omium.org>,
Dylan Reid <dgreid@...gle.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: soc-core: Fix null pointer
dereference in soc_find_component
On Thu, Jan 24, 2019 at 01:07:17PM -0600, Pierre-Louis Bossart wrote:
> Thanks for the feedback, will send a formal patch with the helper and
> machine driver changes after I test more with the legacy drivers. Do you
> have a preference for one patch that deals with multiple machines drivers in
> one shot, or individual patches? The latter are nicer for backports (e.g.
> for Chrome), the former nicer for maintainers...
More patches is good, it doesn't make a huge difference if I get one big
patch or a series of repetitive patches - big serieses are more of an
issue if they're all different patches needing individual review.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists