From: Linus Walleij <linus.walleij@linaro.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] pinctrl: sh-pfc: sh73a0: Remove unnecessary SoC data allocation
Date: Tue, 23 Sep 2014 15:12:18 +0000 [thread overview]
Message-ID: <CACRpkdZAm1dnXMHXVV5ZEC3VgdCkS402kS+3b-9Kvh0euOAE5w@mail.gmail.com> (raw)
In-Reply-To: <1410386155-3896-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Wed, Sep 10, 2014 at 11:55 PM, Laurent Pinchart
<laurent.pinchart+renesas@ideasonboard.com> wrote:
> The SoC data structure allocated at init time only holds a regulator
> pointer that is only used in the init function. Replace it with a local
> variable and get rid of the SoC data structure allocation altogether.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Patch applied with Geert's ACK.
Yours,
Linus Walleij
prev parent reply other threads:[~2014-09-23 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 21:55 [PATCH v2] pinctrl: sh-pfc: sh73a0: Remove unnecessary SoC data allocation Laurent Pinchart
2014-09-11 7:12 ` Geert Uytterhoeven
2014-09-13 20:45 ` Laurent Pinchart
2014-09-23 15:12 ` Linus Walleij [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=CACRpkdZAm1dnXMHXVV5ZEC3VgdCkS402kS+3b-9Kvh0euOAE5w@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-sh@vger.kernel.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).