From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: drivers@analog.com, alsa-devel@alsa-project.org,
Mike Frysinger <vapier@gentoo.org>,
linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
Andrew Morton <akpm@linux-foundation.org>,
stable@kernel.org
Subject: Re: [PATCH v2 1/7] firmware: Sigma: Prevent out of bounds memory access
Date: Tue, 29 Nov 2011 12:02:25 +0000 [thread overview]
Message-ID: <20111129120224.GL2851@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4ED4B17C.3090905@metafoo.de>
On Tue, Nov 29, 2011 at 11:18:36AM +0100, Lars-Peter Clausen wrote:
> He acked some patches this morning. As far as I can see all of the patches
> do have his acked-by now.
Oh, so he has - applied now.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: drivers@analog.com, alsa-devel@alsa-project.org,
Mike Frysinger <vapier@gentoo.org>,
linux-kernel@vger.kernel.org, stable@kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [alsa-devel] [PATCH v2 1/7] firmware: Sigma: Prevent out of bounds memory access
Date: Tue, 29 Nov 2011 12:02:25 +0000 [thread overview]
Message-ID: <20111129120224.GL2851@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4ED4B17C.3090905@metafoo.de>
On Tue, Nov 29, 2011 at 11:18:36AM +0100, Lars-Peter Clausen wrote:
> He acked some patches this morning. As far as I can see all of the patches
> do have his acked-by now.
Oh, so he has - applied now.
next prev parent reply other threads:[~2011-11-29 12:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 8:44 [PATCH v2 1/7] firmware: Sigma: Prevent out of bounds memory access Lars-Peter Clausen
2011-11-28 8:44 ` Lars-Peter Clausen
2011-11-28 8:44 ` [PATCH v2 2/7] firmware: Sigma: Skip header during CRC generation Lars-Peter Clausen
2011-11-28 8:44 ` Lars-Peter Clausen
2011-11-29 5:12 ` Mike Frysinger
2011-11-29 5:12 ` Mike Frysinger
2011-11-28 8:44 ` [PATCH v2 3/7] firmware: Sigma: Fix endianess issues Lars-Peter Clausen
2011-11-28 8:44 ` Lars-Peter Clausen
2011-11-28 8:44 ` [PATCH v2 4/7] ASoC: Move SigmaDSP firmware loader to ASoC Lars-Peter Clausen
2011-11-28 8:44 ` Lars-Peter Clausen
2011-11-28 8:44 ` [PATCH v2 5/7] ASoC: SigmaDSP: Provide diagnostic error messages Lars-Peter Clausen
2011-11-28 8:44 ` Lars-Peter Clausen
2011-11-29 5:12 ` Mike Frysinger
2011-11-28 8:44 ` [PATCH v2 6/7] ASoC: SigmaDSP: Move private structs and functions to C file Lars-Peter Clausen
2011-11-28 8:44 ` Lars-Peter Clausen
2011-11-28 8:44 ` [PATCH v2 7/7] ASoC: SigmaDSP: Add regmap support Lars-Peter Clausen
2011-11-28 8:44 ` Lars-Peter Clausen
2011-11-29 5:17 ` Mike Frysinger
2011-11-29 5:17 ` Mike Frysinger
2011-11-29 5:12 ` [PATCH v2 1/7] firmware: Sigma: Prevent out of bounds memory access Mike Frysinger
2011-11-29 5:12 ` Mike Frysinger
2011-11-29 10:12 ` Mark Brown
2011-11-29 10:12 ` Mark Brown
2011-11-29 10:18 ` [alsa-devel] " Lars-Peter Clausen
2011-11-29 12:02 ` Mark Brown [this message]
2011-11-29 12:02 ` 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=20111129120224.GL2851@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=drivers@analog.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=stable@kernel.org \
--cc=vapier@gentoo.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 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.