From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
lgirdwood@gmail.com, ranjani.sridharan@linux.intel.com,
daniel.baluta@nxp.com
Subject: Re: [PATCH 0/5] ASoC: SOF: fix kcontrol size checks
Date: Thu, 24 Sep 2020 14:30:23 +0300 (EEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2009241426320.3186@eliteleevi.tm.intel.com> (raw)
In-Reply-To: <20200924105645.GA4754@sirena.org.uk>
Hey,
On Thu, 24 Sep 2020, Mark Brown wrote:
> On Thu, Sep 24, 2020 at 08:45:30AM +0300, Kai Vehmanen wrote:
> > I wonder what happened here...? Patches 4 and 5 didn't end up applied
> > although they were in the sent series. I can send them again no prob, but
> > wondering if there was something wrong in the original series, so I can
> > avoid the problem in the future.
>
> Do those patches actually apply to for-5.10 or are they correcting
> issues that only exist in for-5.9?
yes, the series was based on broonie/for-5.10 for sending, and I tested
again and both of the dropped patches still apply on top of for-5.10. They
do not apply cleanly on top of for-5.9.
Br, Kai
next prev parent reply other threads:[~2020-09-24 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 11:08 [PATCH 0/5] ASoC: SOF: fix kcontrol size checks Kai Vehmanen
2020-09-21 11:08 ` [PATCH 1/5] ASoC: SOF: control: fix size checks for ext_bytes control .get() Kai Vehmanen
2020-09-21 11:08 ` [PATCH 2/5] ASoC: SOF: control: fix size checks for volatile " Kai Vehmanen
2020-09-21 11:08 ` [PATCH 3/5] ASoC: SOF: control: add size checks for ext_bytes control .put() Kai Vehmanen
2020-09-21 11:08 ` [PATCH 4/5] ASoC: SOF: control: remove const in sizeof() Kai Vehmanen
2020-09-21 11:08 ` [PATCH 5/5] ASoC: SOF: topology: " Kai Vehmanen
2020-09-22 0:05 ` [PATCH 0/5] ASoC: SOF: fix kcontrol size checks Mark Brown
2020-09-24 5:45 ` Kai Vehmanen
2020-09-24 10:56 ` Mark Brown
2020-09-24 11:30 ` Kai Vehmanen [this message]
2020-09-24 11:35 ` Mark Brown
2020-09-24 14:26 ` Kai Vehmanen
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=alpine.DEB.2.22.394.2009241426320.3186@eliteleevi.tm.intel.com \
--to=kai.vehmanen@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.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.