From: Jonathan Cameron <jic23@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Bastien Nocera <hadess@hadess.net>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 0/3] iio: add labels with accel-location to bmc150 and kxcjk-1013 drivers
Date: Mon, 15 Feb 2021 12:37:38 +0000 [thread overview]
Message-ID: <20210215123738.40416763@archlinux> (raw)
In-Reply-To: <9f3dfd69-c0cc-13d1-d7b5-738387dcb9e4@redhat.com>
On Fri, 12 Feb 2021 19:39:11 +0100
Hans de Goede <hdegoede@redhat.com> wrote:
> Hi,
>
> On 2/12/21 7:33 PM, Jonathan Cameron wrote:
> > On Sun, 7 Feb 2021 17:08:58 +0100
> > Hans de Goede <hdegoede@redhat.com> wrote:
> >
> >> Hi All,
> >>
> >> Here is a patch-set implementing the standardized "accel-display"
> >> and "accel-base" label sysfs-attributes defined in my earlier
> >> "[PATCH 1/2] iio: documentation: Document proximity sensor label use"
> >> "[PATCH 2/2] iio: documentation: Document accelerometer label use"
> >> series.
> >>
> >> This patch sets adds these labels to the bmc150 and kxcjk-1013 accel
> >> drivers.
> > Series applied to the togreg branch of iio.git and pushed out as testing
> > for the autobuilders to poke at it.
>
> Thanks, much appreciated.
>
> But this was sorta a follow-up to:
>
> [PATCH 1/2] iio: documentation: Document proximity sensor label use
> [PATCH 2/2] iio: documentation: Document accelerometer label use
>
> Where 2/2 defines the standardized label values which this series uses
> and AFAIK those have not been merged yet?
>
> I guess we can always fix the labels if discussion surrounding those
> leads to standardizing on different label contents for this. But if
> the discussion surrounding those results in the conclusion to not
> use labels for this at all, while we already have this merged, then
> we probably need to revert 2/3 and 3/3 of this series...
>
> But maybe I just missed the 2 documentation patches getting merged ?
Understood. The changes for the docs patch that I was looking for
are just editorial, so I wasn't that fussed if it goes in slightly out of
order.
Jonathan
>
> > Note we are almost certainly too late for coming merge window so this
> > will be next time around.
>
> That is fine.
>
> Regards,
>
> Hans
>
prev parent reply other threads:[~2021-02-15 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 16:08 [PATCH 0/3] iio: add labels with accel-location to bmc150 and kxcjk-1013 drivers Hans de Goede
2021-02-07 16:08 ` [PATCH 1/3] iio: core: Allow drivers to specify a label without it coming from of Hans de Goede
2021-02-08 7:27 ` Alexandru Ardelean
2021-02-07 16:09 ` [PATCH 2/3] iio: accel: bmc150: Set label based on accel-location on 2-accel yoga-style 2-in-1s Hans de Goede
2021-02-07 16:09 ` [PATCH 3/3] iio: accel: kxcjk-1013: " Hans de Goede
2021-02-12 18:33 ` [PATCH 0/3] iio: add labels with accel-location to bmc150 and kxcjk-1013 drivers Jonathan Cameron
2021-02-12 18:39 ` Hans de Goede
2021-02-15 12:37 ` Jonathan Cameron [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=20210215123738.40416763@archlinux \
--to=jic23@kernel.org \
--cc=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).