Linux IIO development
 help / color / mirror / Atom feed
From: "Maxwell Doose" <m32285159@gmail.com>
To: "Jonathan Cameron" <jic23@kernel.org>, <linux-iio@vger.kernel.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Subject: Re: IIO: Merged in v7.2-rc2 + anyone have comments on whether to ask for sashiko emails to the list?
Date: Mon, 06 Jul 2026 12:45:04 -0500	[thread overview]
Message-ID: <DJROBQ66JZHX.5QSG0W2J2CWQ@gmail.com> (raw)
In-Reply-To: <20260706173541.4f25ad81@jic23-huawei>

[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]

On Mon Jul 6, 2026 at 11:35 AM CDT
Jonathan Cameron <jic23@kernel.org> wrote:

> Hi All,
>
> Note that I've just pushed the testing branch out with v7.2-rc2 merged
> in.  There were 3 conflicts due to Uwe's work on restructuring the
> headers for device_id tables.  Note I haven't (yet anyway) updated
> the 7 additions of mod_devicetable.h that crossed with his patch set
> as I didn't want to complicate the merge.
>
> For new work this cycle please base either on v7.2-rc2 or on top of
> my togreg branch (assuming no problems that will have this merge sometime
> later this week). This should only make much difference for new drivers,
> or for any IWYU / header improvement patches.
>
> On another topic. Personally I'm reasonably impressed with Sashiko's
> feedback. However it is far from perfect and I'm a little concerned
> that new folk might not treat it with appropriate caution.
>
> What do people feel about me asking them to enable sending replies 
> directly to the list?
>

Regarding sashiko reviews on the mailing list, because IIO seems to get
plenty of new contributors every cycle I'm also tad concerned that new
contributors will take the sashiko advice every time without putting
enough research into it. It's probably better if someone else (who's
more experienced) looks into the sashiko review and gives them the link
once they can verify as we've been doing previously. On the contrary I'm
not totally opposed to it and I think it would be fairly helpful for
most people.

-- 
best regards,
max


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]

  reply	other threads:[~2026-07-06 17:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 16:35 IIO: Merged in v7.2-rc2 + anyone have comments on whether to ask for sashiko emails to the list? Jonathan Cameron
2026-07-06 17:45 ` Maxwell Doose [this message]
2026-07-06 20:12 ` Joshua Crofts

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=DJROBQ66JZHX.5QSG0W2J2CWQ@gmail.com \
    --to=m32285159@gmail.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=u.kleine-koenig@baylibre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox