From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
Hans de Goede <hdegoede@redhat.com>,
~postmarketos/upstreaming@lists.sr.ht,
Nikita Travkin <nikita@trvn.ru>
Subject: Re: [PATCH 0/4] iio: accel: bmc150: Add support for INT2 and BMC156
Date: Mon, 19 Jul 2021 15:34:50 +0300 [thread overview]
Message-ID: <CAHp75Ve-mK59bOt+am2GGXww=vf-BhXmpwCeKvX8rph9tRr3FQ@mail.gmail.com> (raw)
In-Reply-To: <20210719112156.27087-1-stephan@gerhold.net>
On Mon, Jul 19, 2021 at 2:26 PM Stephan Gerhold <stephan@gerhold.net> wrote:
>
> This series makes it possible to set up interrupts with the BMC150 driver
> on boards where only the INT2 pin is connected (and not INT1). This is
> particularly always the case for BMC156 since for some reason it only
> has the INT2 pin and not the INT1 pin.
>
> These changes were already partially discussed here:
> https://lore.kernel.org/linux-iio/YMOphuXSoODIVX06@gerhold.net/
I forgot the story, but the series sounds to me like déjà-vu. Please,
remind me if it was sent once before? If yes, then this one misses
version bumping and/or changelog.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-07-19 12:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 11:21 [PATCH 0/4] iio: accel: bmc150: Add support for INT2 and BMC156 Stephan Gerhold
2021-07-19 11:21 ` [PATCH 1/4] dt-bindings: iio: accel: bma255: Add interrupt-names Stephan Gerhold
2021-07-19 13:57 ` Linus Walleij
2021-07-24 16:00 ` Jonathan Cameron
2021-07-19 11:21 ` [PATCH 2/4] dt-bindings: iio: accel: bma255: Add bosch,bmc156_accel Stephan Gerhold
2021-07-19 13:58 ` Linus Walleij
2021-07-24 16:03 ` Jonathan Cameron
2021-07-29 19:10 ` Rob Herring
2021-07-29 19:10 ` Rob Herring
2021-07-19 11:21 ` [PATCH 3/4] iio: accel: bmc150: Make it possible to configure INT2 instead of INT1 Stephan Gerhold
2021-07-19 14:07 ` Linus Walleij
2021-07-19 15:01 ` Andy Shevchenko
2021-07-19 15:10 ` Stephan Gerhold
2021-07-19 16:19 ` Andy Shevchenko
2021-07-19 17:26 ` Stephan Gerhold
2021-07-19 18:05 ` Andy Shevchenko
2021-07-19 18:36 ` Stephan Gerhold
2021-07-20 15:04 ` Andy Shevchenko
2021-07-24 16:19 ` Jonathan Cameron
2021-07-24 18:06 ` Jonathan Cameron
2021-07-19 11:21 ` [PATCH 4/4] iio: accel: bmc150: Add support for BMC156 Stephan Gerhold
2021-07-19 14:08 ` Linus Walleij
2021-07-24 16:12 ` Jonathan Cameron
2021-07-27 18:32 ` Stephan Gerhold
2021-07-31 18:04 ` Jonathan Cameron
2021-07-19 12:34 ` Andy Shevchenko [this message]
2021-07-19 12:42 ` [PATCH 0/4] iio: accel: bmc150: Add support for INT2 and BMC156 Stephan Gerhold
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='CAHp75Ve-mK59bOt+am2GGXww=vf-BhXmpwCeKvX8rph9tRr3FQ@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).