From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Gwendal Grignou <gwendal@chromium.org>,
Jonathan Cameron <jic23@kernel.org>,
linux-iio <linux-iio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Denis Ciocca <denis.ciocca@st.com>
Subject: Re: [PATCH 13/13] iio:st-sensors: Move exports into ST_SENSORS namespace
Date: Thu, 6 Jan 2022 14:48:07 +0000 [thread overview]
Message-ID: <20220106144807.0000756c@Huawei.com> (raw)
In-Reply-To: <CAHp75VcQjdgLe2fX23g9UOneQXQrrkGWwpTqD=0bgq+K3B+ZNw@mail.gmail.com>
On Thu, 6 Jan 2022 16:42:56 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Thu, Jan 6, 2022 at 3:41 PM Jonathan Cameron
> <Jonathan.Cameron@huawei.com> wrote:
> > On Wed, 5 Jan 2022 10:43:49 -0800
> > Gwendal Grignou <gwendal@chromium.org> wrote:
> > > On Thu, Dec 30, 2021 at 11:28 AM Jonathan Cameron <jic23@kernel.org> wrote:
>
> > Could do IIO_ST_SENSORS perhaps?
>
> You guys beat me up to it, I also came here to make the very same comment.
> +1 to IIO_ST_SENSORS.
>
I'm coming round to prefixing the lot with IIO_ rather than just the ones
that aren't 'part' specific. Seems easier than having a vague naming scheme
and I can't see any harm from doing so.
Anyone disagree?
Jonathan
next prev parent reply other threads:[~2022-01-06 14:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 19:33 [PATCH 00/13] IIO: accel/st-sensors move into separate symbol namespaces Jonathan Cameron
2021-12-30 19:33 ` [PATCH 01/13] iio:accel:mma9551_core: Move exports into MMA9551 namespace Jonathan Cameron
2021-12-30 19:33 ` [PATCH 02/13] iio:accel:mma7455_core: Move exports into MMA7455 namespace Jonathan Cameron
2021-12-31 10:41 ` Uwe Kleine-König
2021-12-31 18:40 ` Jonathan Cameron
2021-12-30 19:33 ` [PATCH 03/13] iio:accel:kxsd9: Move exports into KDSD9 namespace Jonathan Cameron
2021-12-30 19:33 ` [PATCH 04/13] iio:accel:bma400: Move exports into BMA400 namespace Jonathan Cameron
2021-12-30 19:33 ` [PATCH 05/13] iio:accel:adxl313: Move exports into ADXL313 namespace Jonathan Cameron
2021-12-30 19:33 ` [PATCH 06/13] iio:accel:adxl345: Move exports into ADXL345 namespace Jonathan Cameron
2021-12-30 19:33 ` [PATCH 07/13] iio:accel:adxl355: Move exports into ADXL355 namespace Jonathan Cameron
2021-12-30 19:33 ` [PATCH 08/13] iio:accel:adxl372: Move exports into ADXL372 namespace Jonathan Cameron
2021-12-30 19:33 ` [PATCH 09/13] iio:accel:bmc150: Move exports into BMC150 namespace Jonathan Cameron
2021-12-31 1:40 ` srinivas pandruvada
2021-12-30 19:33 ` [PATCH 10/13] iio:accel:bmi088: Move exports into BMI088 namespace Jonathan Cameron
2021-12-30 19:33 ` [PATCH 11/13] iio:accel:fxl8962af: Move exports into FXL8962AF namespace Jonathan Cameron
2021-12-30 19:33 ` [PATCH 12/13] iio:st-sensors: Remove duplicate MODULE_* Jonathan Cameron
2022-01-02 6:58 ` Linus Walleij
2021-12-30 19:33 ` [PATCH 13/13] iio:st-sensors: Move exports into ST_SENSORS namespace Jonathan Cameron
2022-01-05 18:43 ` Gwendal Grignou
2022-01-06 13:41 ` Jonathan Cameron
2022-01-06 14:42 ` Andy Shevchenko
2022-01-06 14:48 ` Jonathan Cameron [this message]
2022-01-02 6:57 ` [PATCH 00/13] IIO: accel/st-sensors move into separate symbol namespaces 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=20220106144807.0000756c@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=andy.shevchenko@gmail.com \
--cc=denis.ciocca@st.com \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@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).