From: Samuel Ortiz <sameo@linux.intel.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
Anmar Oueja <anmar.oueja@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Loic Pallardy <loic.pallardy@st.com>,
Patrice Chotard <patrice.chotard@st.com>,
Michel Jaouen <michel.jaouen@st.com>
Subject: Re: [PATCH] mfd: prcmu: delete pin control helpers
Date: Tue, 22 Jan 2013 04:25:38 +0100 [thread overview]
Message-ID: <20130122032538.GI7409@sortiz-mobl> (raw)
In-Reply-To: <1357546398-9541-1-git-send-email-linus.walleij@stericsson.com>
Hi Linus,
On Mon, Jan 07, 2013 at 09:13:18AM +0100, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
>
> These static inlines are duplicating the task now done by the
> Nomadik pinctrl drivers, so delete them from the prcmu static
> inlines, also delete the register definitions as these should
> only be known by the pinctrl driver.
>
> Cc: Loic Pallardy <loic.pallardy@st.com>
> Cc: Patrice Chotard <patrice.chotard@st.com>
> Cc: Michel Jaouen <michel.jaouen@st.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Sam, this is a pure clean-up patch following the v3.8 merge
> window. These inlines are completely unused in the kernel and
> I'd simply apply it to the -rc series but it's up to you.
Unless it really makes your life easier, I like to keep my -rc pull requests
for fixes only.
I'll apply it to my for-next branch for now.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2013-01-22 3:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 8:13 [PATCH] mfd: prcmu: delete pin control helpers Linus Walleij
2013-01-22 3:25 ` Samuel Ortiz [this message]
2013-01-22 13:25 ` Linus Walleij
2013-01-27 0:10 ` Samuel Ortiz
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=20130122032538.GI7409@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=anmar.oueja@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.pallardy@st.com \
--cc=michel.jaouen@st.com \
--cc=patrice.chotard@st.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