From: "Woodhouse, David" <david.woodhouse@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Jason Cooper <jason@lakedaemon.net>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Andrew Lunn <andrew@lunn.ch>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] pinctrl: mvebu: prevent walking off the end of group array
Date: Wed, 27 Mar 2013 22:11:53 +0000 [thread overview]
Message-ID: <1364422304.14860.9.camel@i7.infradead.org> (raw)
In-Reply-To: <CACRpkdb-CdmzszyixBLGdZjXJXzef26u0qN9xWcrYa3JbAD3Ow@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
On Wed, 2013-03-27 at 23:06 +0100, Linus Walleij wrote:
> Is it so critical that it needs to be tagged for stable as well
> then tell me.
>
> If it's non-critical enough to live on for -next then tell me.
I don't think it's critical. It'll probably never trigger in practice.
--
Sent with MeeGo's ActiveSync support.
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6242 bytes --]
next prev parent reply other threads:[~2013-03-27 22:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 15:58 memory leak and other oddness in pinctrl-mvebu.c David Woodhouse
2013-03-09 8:49 ` Sebastian Hesselbarth
2013-03-09 19:02 ` David Woodhouse
2013-03-09 19:46 ` Sebastian Hesselbarth
2013-03-09 22:53 ` Jason Cooper
2013-03-09 23:39 ` David Woodhouse
2013-03-10 0:06 ` Jason Cooper
2013-03-13 16:59 ` Linus Walleij
2013-03-13 17:35 ` [PATCH] pinctrl: mvebu: prevent walking off the end of group array Jason Cooper
2013-03-13 17:47 ` Linus Walleij
2013-03-13 17:50 ` Jason Cooper
2013-03-13 18:40 ` Linus Walleij
2013-03-13 17:48 ` Sebastian Hesselbarth
2013-03-13 17:48 ` [PATCH V2] " Jason Cooper
2013-03-14 10:29 ` David Woodhouse
2013-03-16 11:44 ` [PATCH v3] " Sebastian Hesselbarth
2013-03-22 16:39 ` Jason Cooper
2013-03-27 22:06 ` Linus Walleij
2013-03-27 22:11 ` Woodhouse, David [this message]
2013-03-27 22:34 ` Linus Walleij
2013-03-28 11:08 ` Jason Cooper
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=1364422304.14860.9.camel@i7.infradead.org \
--to=david.woodhouse@intel.com \
--cc=andrew@lunn.ch \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=swarren@wwwdotorg.org \
--cc=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®