From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Daniel Baluta <daniel.baluta@intel.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 1/4] staging:iio:ad5933: Fix NULL pointer deref when enabling buffer
Date: Sat, 27 Sep 2014 22:35:45 +0200 [thread overview]
Message-ID: <54271FA1.7050902@metafoo.de> (raw)
In-Reply-To: <542684D9.3010703@kernel.org>
On 09/27/2014 11:35 AM, Jonathan Cameron wrote:
>> Fixes: 959d2952d124 ("staging:iio: make iio_sw_buffer_preenable much more general.")
>> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> Yikes, that was some time ago. Anyhow, applied to the fixes-togreg branch of
> iio.git
> though given timing it won't go in until after the merge window.
> Also marked for stable.
Thanks.
>
> I'm not 100% sure how one marks a patch as for only onwards from a particular tree.
> There is syntax for saying cherry pick. Hopefully the fixes tag will do the job.
Yes, the fixes tag usually does the right thing.
prev parent reply other threads:[~2014-09-27 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 14:27 [PATCH v2 1/4] staging:iio:ad5933: Fix NULL pointer deref when enabling buffer Lars-Peter Clausen
2014-09-25 14:27 ` [PATCH v2 2/4] staging:iio:ad5933: Drop "raw" from channel names Lars-Peter Clausen
2014-09-25 14:27 ` [PATCH v2 3/4] staging:iio:ad5933: Report temperature as raw value Lars-Peter Clausen
2014-09-27 9:52 ` Jonathan Cameron
2015-01-04 17:55 ` Jonathan Cameron
2014-09-25 14:27 ` [PATCH v2 4/4] staging:iio:ad5933: Remove platform data from state struct Lars-Peter Clausen
2015-01-04 17:55 ` Jonathan Cameron
2014-09-27 9:35 ` [PATCH v2 1/4] staging:iio:ad5933: Fix NULL pointer deref when enabling buffer Jonathan Cameron
2014-09-27 20:35 ` Lars-Peter Clausen [this message]
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=54271FA1.7050902@metafoo.de \
--to=lars@metafoo.de \
--cc=daniel.baluta@intel.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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.