From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] i2c:at91: add bound checking on SMBus block length bytes
Date: Mon, 27 Oct 2014 08:57:49 +0100 [thread overview]
Message-ID: <20141027075749.GA1284@katana> (raw)
In-Reply-To: <20141023134927.GQ7443@ldesroches-Latitude-E6320>
> > Wolfram took in the patch quietly awhile back. It's in the 3.17 kernel
> > and backported to some of the older trees.
> > https://github.com/torvalds/linux/commit/75b81f339c6af43f6f4a1b3eabe0603321dade65
>
> Great, sorry for the noise so. It seems I have checked it from a wrong
> branch.
Yes, usually I send out mails when applying patches. Dunno why I missed
it here.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141027/9cec37aa/attachment.sig>
prev parent reply other threads:[~2014-10-27 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 1:39 [PATCH v2] i2c:at91: add bound checking on SMBus block length bytes Marek Roszko
2014-10-21 7:14 ` Ludovic Desroches
2014-10-23 13:28 ` Mark Roszko
2014-10-23 13:49 ` Ludovic Desroches
2014-10-27 7:57 ` Wolfram Sang [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=20141027075749.GA1284@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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).