From: Joshua Crofts <joshua.crofts1@gmail.com>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Svyatoslav Ryhel" <clamor95@gmail.com>,
"David Heidelberg" <david@ixit.cz>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] iio: light: al3xxx: add missing REGMAP_I2C to Kconfig entries
Date: Fri, 26 Jun 2026 16:28:02 +0200 [thread overview]
Message-ID: <20260626162802.0000716b@gmail.com> (raw)
In-Reply-To: <aj6EhyuOxBqDDf0X@nsa>
On Fri, 26 Jun 2026 14:57:05 +0100
Nuno Sá <noname.nuno@gmail.com> wrote:
> I'm not sure we have a defined policy for that in IIO. Now that you
> mention it, maybe time to ask...
>
> My understanding always was that Jonathan takes care of Ccing stable
> but maybe he just does it and being nice about it, does not complain :).
>
> So, Jonathan,
>
> Should the sender take care about Cc or not? Or it does not really matter
> :)?
I always add a Cc: stable when submitting bugfixes, only this time I
forgot :P In the end Jonathan decides whether it should be marked for
stable so he can just remove the tag if the fix isn't backport-worthy.
--
Kind regards
CJD
prev parent reply other threads:[~2026-06-26 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 19:38 [PATCH v2 0/3] iio: light: al3xxx: add missing REGMAP_I2C to Kconfig entries Joshua Crofts
2026-06-25 19:38 ` [PATCH v2 1/3] iio: light: al3000a: add missing REGMAP_I2C to Kconfig Joshua Crofts
2026-06-25 19:38 ` [PATCH v2 2/3] iio: light: al3010: " Joshua Crofts
2026-06-25 19:38 ` [PATCH v2 3/3] iio: light: al3320a: " Joshua Crofts
2026-06-25 19:50 ` [PATCH v2 0/3] iio: light: al3xxx: add missing REGMAP_I2C to Kconfig entries David Heidelberg
2026-06-26 12:26 ` Andy Shevchenko
2026-06-26 12:38 ` Joshua Crofts
2026-06-26 13:57 ` Nuno Sá
2026-06-26 14:13 ` Andy Shevchenko
2026-06-26 14:28 ` Joshua Crofts [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=20260626162802.0000716b@gmail.com \
--to=joshua.crofts1@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=clamor95@gmail.com \
--cc=david@ixit.cz \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noname.nuno@gmail.com \
--cc=nuno.sa@analog.com \
/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.