From: Linus Walleij <linus.walleij@linaro.org>
To: Fabio Baltieri <fabio.baltieri@linaro.org>
Cc: Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: ux500: read the correct soc_id number
Date: Mon, 4 Mar 2013 07:14:37 +0100 [thread overview]
Message-ID: <CACRpkdbF0gjGt2BxzwAAxjWqGbybuzne+43vSKUiH_tqLQTFPQ@mail.gmail.com> (raw)
In-Reply-To: <1361348956-4387-1-git-send-email-fabio.baltieri@linaro.org>
On Wed, Feb 20, 2013 at 9:29 AM, Fabio Baltieri
<fabio.baltieri@linaro.org> wrote:
> Fix db8500_read_soc_id() to read all five soc_id number locations
> instead of repeating the second one two times.
>
> Signed-off-by: Fabio Baltieri <fabio.baltieri@linaro.org>
Thanks, patch applied!
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ux500: read the correct soc_id number
Date: Mon, 4 Mar 2013 07:14:37 +0100 [thread overview]
Message-ID: <CACRpkdbF0gjGt2BxzwAAxjWqGbybuzne+43vSKUiH_tqLQTFPQ@mail.gmail.com> (raw)
In-Reply-To: <1361348956-4387-1-git-send-email-fabio.baltieri@linaro.org>
On Wed, Feb 20, 2013 at 9:29 AM, Fabio Baltieri
<fabio.baltieri@linaro.org> wrote:
> Fix db8500_read_soc_id() to read all five soc_id number locations
> instead of repeating the second one two times.
>
> Signed-off-by: Fabio Baltieri <fabio.baltieri@linaro.org>
Thanks, patch applied!
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-03-04 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 8:29 [PATCH] ARM: ux500: read the correct soc_id number Fabio Baltieri
2013-02-20 8:29 ` Fabio Baltieri
2013-03-04 6:14 ` Linus Walleij [this message]
2013-03-04 6:14 ` Linus Walleij
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=CACRpkdbF0gjGt2BxzwAAxjWqGbybuzne+43vSKUiH_tqLQTFPQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=fabio.baltieri@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinidhi.kasagar@stericsson.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.