From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Timur Tabi <timur@codeaurora.org>,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
thierry.reding@gmail.com, Stephen Boyd <sboyd@codeaurora.org>,
david.brown@linaro.org, andy.gross@linaro.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Varadarajan Narayanan <varada@codeaurora.org>,
Archit Taneja <architt@codeaurora.org>
Subject: Re: [PATCH 4/4] [v4] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002
Date: Wed, 13 Dec 2017 16:32:15 +0200 [thread overview]
Message-ID: <1513175535.7000.10.camel@linux.intel.com> (raw)
In-Reply-To: <bae16fa3-1bdf-74b1-97b7-f6b2db212621@codeaurora.org>
On Tue, 2017-12-12 at 14:17 -0600, Timur Tabi wrote:
> On 12/12/2017 04:05 AM, Andy Shevchenko wrote:
> > > +static const struct acpi_device_id qdf2xxx_acpi_ids[] = {
> > > + {"QCOM8001", QDF2XXX_V1},
> > > + {"QCOM8002", QDF2XXX_V2},
> > > + {},
> > > +};
> > > +MODULE_DEVICE_TABLE(acpi, qdf2xxx_acpi_ids);
> > >
> > > + const struct acpi_device_id *id =
> > > + acpi_match_device(qdf2xxx_acpi_ids, &pdev->dev);
> >
> > JFYI: there is no need to move IDs like this.
> > Use members of struct device_driver wisely.
>
> I have to move it, otherwise I get:
>
> drivers/pinctrl/qcom/pinctrl-qdf2xxx.c:49:21: error:
> 'qdf2xxx_acpi_ids'
> undeclared (first use in this function); did you mean
> 'qdf2xxx_pinctrl'?
>
> I reference the structure in qdf2xxx_pinctrl_probe().
Please, read my comment again. The key part of the phrase:
"Use members of struct device_driver"
So, do not move the IDs. There are examples in the kernel how to access
it.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
WARNING: multiple messages have this Message-ID (diff)
From: andriy.shevchenko@linux.intel.com (Andy Shevchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] [v4] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002
Date: Wed, 13 Dec 2017 16:32:15 +0200 [thread overview]
Message-ID: <1513175535.7000.10.camel@linux.intel.com> (raw)
In-Reply-To: <bae16fa3-1bdf-74b1-97b7-f6b2db212621@codeaurora.org>
On Tue, 2017-12-12 at 14:17 -0600, Timur Tabi wrote:
> On 12/12/2017 04:05 AM, Andy Shevchenko wrote:
> > > +static const struct acpi_device_id qdf2xxx_acpi_ids[] = {
> > > + {"QCOM8001", QDF2XXX_V1},
> > > + {"QCOM8002", QDF2XXX_V2},
> > > + {},
> > > +};
> > > +MODULE_DEVICE_TABLE(acpi, qdf2xxx_acpi_ids);
> > >
> > > + const struct acpi_device_id *id =
> > > + acpi_match_device(qdf2xxx_acpi_ids, &pdev->dev);
> >
> > JFYI: there is no need to move IDs like this.
> > Use members of struct device_driver wisely.
>
> I have to move it, otherwise I get:
>
> drivers/pinctrl/qcom/pinctrl-qdf2xxx.c:49:21: error:
> 'qdf2xxx_acpi_ids'
> undeclared (first use in this function); did you mean
> 'qdf2xxx_pinctrl'?
>
> I reference the structure in qdf2xxx_pinctrl_probe().
Please, read my comment again. The key part of the phrase:
"Use members of struct device_driver"
So, do not move the IDs. There are examples in the kernel how to access
it.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-12-13 14:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 23:28 [PATCH 0/4] [v8] pinctrl: qcom: add support for sparse GPIOs Timur Tabi
2017-12-01 23:28 ` Timur Tabi
2017-12-01 23:28 ` [PATCH 1/4] [v2] Revert "gpio: set up initial state from .get_direction()" Timur Tabi
2017-12-01 23:28 ` Timur Tabi
2017-12-01 23:28 ` [PATCH 2/4] [v2] gpiolib: add bitmask for valid GPIO lines Timur Tabi
2017-12-01 23:28 ` Timur Tabi
2017-12-12 9:58 ` Andy Shevchenko
2017-12-12 9:58 ` Andy Shevchenko
2017-12-12 20:16 ` Timur Tabi
2017-12-12 20:16 ` Timur Tabi
2017-12-01 23:28 ` [PATCH 3/4] [v7] pinctrl: qcom: disable GPIO groups with no pins Timur Tabi
2017-12-01 23:28 ` Timur Tabi
2017-12-01 23:28 ` [PATCH 4/4] [v4] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002 Timur Tabi
2017-12-01 23:28 ` Timur Tabi
2017-12-12 10:05 ` Andy Shevchenko
2017-12-12 10:05 ` Andy Shevchenko
2017-12-12 20:17 ` Timur Tabi
2017-12-12 20:17 ` Timur Tabi
2017-12-13 14:32 ` Andy Shevchenko [this message]
2017-12-13 14:32 ` Andy Shevchenko
2017-12-13 14:46 ` Timur Tabi
2017-12-13 14:46 ` Timur Tabi
2017-12-13 15:18 ` Timur Tabi
2017-12-13 15:18 ` Timur Tabi
2017-12-13 15:40 ` Andy Shevchenko
2017-12-13 15:40 ` Andy Shevchenko
[not found] ` <1512170904-4749-5-git-send-email-timur-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-12-12 10:42 ` Linus Walleij
2017-12-12 10:42 ` Linus Walleij
2017-12-12 11:07 ` Andy Shevchenko
2017-12-12 11:07 ` Andy Shevchenko
2017-12-12 20:27 ` Timur Tabi
2017-12-12 20:27 ` Timur Tabi
2017-12-13 14:36 ` Andy Shevchenko
2017-12-13 14:36 ` Andy Shevchenko
2017-12-13 14:47 ` Timur Tabi
2017-12-13 14:47 ` Timur Tabi
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=1513175535.7000.10.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy.gross@linaro.org \
--cc=architt@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=sboyd@codeaurora.org \
--cc=thierry.reding@gmail.com \
--cc=timur@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 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.