From: Samuel Ortiz <sameo@linux.intel.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] mfd/abx500: fix missing abx500 header file updates
Date: Mon, 31 Oct 2011 00:02:18 +0100 [thread overview]
Message-ID: <20111030230218.GK3897@sortiz-mobl> (raw)
In-Reply-To: <1319804135-2740-1-git-send-email-linus.walleij@stericsson.com>
Hi Linus,
On Fri, Oct 28, 2011 at 02:15:35PM +0200, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
>
> I missed to include a patch adding the new silicon revision define
> CUT3P3 and remove the retired CUT0 versions of AB8500. Also delete
> the reference to the retired AB3550 from the header.
Thanks. I had to apply it manually as the first chunk would not apply against
my for-next branch, but I pushed the actual fix now.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2011-10-30 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 12:15 [PATCH] mfd/abx500: fix missing abx500 header file updates Linus Walleij
2011-10-30 17:57 ` Randy Dunlap
2011-10-30 23:02 ` Samuel Ortiz [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=20111030230218.GK3897@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox