From: Bjorn Andersson <bjorn@kryo.se>
To: Matthew McClintock <mmcclint@qca.qualcomm.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Andy Gross <agross@codeaurora.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Varadarajan Narayanan <varada@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
qca-upstream.external@qca.qualcomm.com,
Sricharan R <sricharan@codeaurora.org>,
Mathieu Olivari <mathieu@codeaurora.org>,
Matthew McClintock <mmcclint@codeaurora.org>
Subject: Re: [PATCH v3 1/6] pinctrl: qcom: ipq4019: Add IPQ4019 pinctrl support
Date: Sun, 14 Feb 2016 16:41:12 -0800 [thread overview]
Message-ID: <CAJAp7Oib4xJEHoxiwwGhOhcD3WG4AfdCGGVNqmit+Y6LGnkgoA@mail.gmail.com> (raw)
In-Reply-To: <1447975173-29485-2-git-send-email-mmcclint@qca.qualcomm.com>
On Thu, Nov 19, 2015 at 3:19 PM, Matthew McClintock
<mmcclint@qca.qualcomm.com> wrote:
> From: Varadarajan Narayanan <varada@codeaurora.org>
>
> Add pinctrl driver support for IPQ4019 platform
>
> Signed-off-by: Sricharan R <sricharan@codeaurora.org>
> Signed-off-by: Mathieu Olivari <mathieu@codeaurora.org>
> Signed-off-by: Varadarajan Narayanan <varada@codeaurora.org>
> Signed-off-by: Matthew McClintock <mmcclint@codeaurora.org>
> ---
I was asked to review this, to make sure that Linus wasn't waiting for
my ack or anything. But now I see that you have not added him as a
recipient. Please make sure to run ./scripts/get_maintainer.pl and
pick appropriate recipients in the future.
>
> v3
> - update example with actual values from dts
> - add missing pins 71-99
> - drop many functions and stick to basic functionality
>
I hope to see a patch later on adding all those functions back, but
that's fine with me.
[..]
> +static struct platform_driver ipq4019_pinctrl_driver = {
> + .driver = {
> + .name = "ipq4019-pinctrl",
> + .owner = THIS_MODULE,
platform_drivers do get their .owner assigned by platform_drive_register().
> + .of_match_table = ipq4019_pinctrl_of_match,
> + },
> + .probe = ipq4019_pinctrl_probe,
> + .remove = msm_pinctrl_remove,
> +};
Part of the .owner above you have my
Acked-by: Bjorn Andersson <bjorn.andersson@linaro.org>
@Linus, this still applies and builds cleanly on linux-next.
Would you be okay dropping the owner assignment while applying this patch?
Regards,
Bjorn
next prev parent reply other threads:[~2016-02-15 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1447975173-29485-1-git-send-email-mmcclint@qca.qualcomm.com>
2015-11-19 23:19 ` [PATCH v3 1/6] pinctrl: qcom: ipq4019: Add IPQ4019 pinctrl support Matthew McClintock
2015-11-20 16:35 ` Rob Herring
2015-12-11 4:03 ` [v3,1/6] " Andy Gross
2016-02-15 0:41 ` Bjorn Andersson [this message]
2016-02-16 14:53 ` [PATCH v3 1/6] " Linus Walleij
2016-02-16 14:54 ` Linus Walleij
2016-02-16 16:31 ` Matthew McClintock
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=CAJAp7Oib4xJEHoxiwwGhOhcD3WG4AfdCGGVNqmit+Y6LGnkgoA@mail.gmail.com \
--to=bjorn@kryo.se \
--cc=agross@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu@codeaurora.org \
--cc=mmcclint@codeaurora.org \
--cc=mmcclint@qca.qualcomm.com \
--cc=qca-upstream.external@qca.qualcomm.com \
--cc=sricharan@codeaurora.org \
--cc=varada@codeaurora.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).