From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] pinctrl: meson: remove unused pin_base
Date: Fri, 06 Oct 2017 16:15:35 -0700 [thread overview]
Message-ID: <7hd15z7trc.fsf@baylibre.com> (raw)
In-Reply-To: <20171006085407.27905-1-jbrunet@baylibre.com> (Jerome Brunet's message of "Fri, 6 Oct 2017 10:54:07 +0200")
Jerome Brunet <jbrunet@baylibre.com> writes:
> While removing the need to have pin_base defined in meson pinctrl
> drivers, I forgot to remove the corresponding field from the
> pinctrl_data structure.
>
> Fixing this now.
>
> Fixes: 70e5ecb1b994 ("pinctrl: meson: get rid of pin_base")
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
Reviewed-by: Kevin Hilman <khilman@baylibre.com>
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Carlo Caione <carlo@caione.org>,
linux-gpio@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: meson: remove unused pin_base
Date: Fri, 06 Oct 2017 16:15:35 -0700 [thread overview]
Message-ID: <7hd15z7trc.fsf@baylibre.com> (raw)
In-Reply-To: <20171006085407.27905-1-jbrunet@baylibre.com> (Jerome Brunet's message of "Fri, 6 Oct 2017 10:54:07 +0200")
Jerome Brunet <jbrunet@baylibre.com> writes:
> While removing the need to have pin_base defined in meson pinctrl
> drivers, I forgot to remove the corresponding field from the
> pinctrl_data structure.
>
> Fixing this now.
>
> Fixes: 70e5ecb1b994 ("pinctrl: meson: get rid of pin_base")
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
Reviewed-by: Kevin Hilman <khilman@baylibre.com>
next prev parent reply other threads:[~2017-10-06 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 8:54 [PATCH] pinctrl: meson: remove unused pin_base Jerome Brunet
2017-10-06 8:54 ` Jerome Brunet
2017-10-06 23:15 ` Kevin Hilman [this message]
2017-10-06 23:15 ` Kevin Hilman
2017-10-11 7:54 ` Linus Walleij
2017-10-11 7:54 ` 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=7hd15z7trc.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@lists.infradead.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 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.