From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: Moksh Panicker <mokshpanicker.7@gmail.com>,
nuno.sa@analog.com, Michael.Hennerich@analog.com,
dlechner@baylibre.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org
Subject: Re: [PATCH v2 0/2] iio: adc: ad7779: Remove dead code and redundant error message
Date: Wed, 1 Jul 2026 01:16:35 +0100 [thread overview]
Message-ID: <20260701011635.30f6bedb@jic23-huawei> (raw)
In-Reply-To: <20260630145327.00001b9f@gmail.com>
On Tue, 30 Jun 2026 14:53:27 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> On Tue, 30 Jun 2026 12:43:04 +0000
> Moksh Panicker <mokshpanicker.7@gmail.com> wrote:
>
> > Thanks for the feedback, I'll fix the blank line and wait before sending v3.
>
> Also, please don't top-post!
>
Also please don't send replies to say you'll do what was suggested. That info
should be in the change log for the next version (or in the case of the slow
down reflected in slowing down ;) Replying like was done here just adds noise
to the mailing list. It's a common mistake for new contributors so don't worry
too much about it being pointed out to you specifically!
I've just sent a note on this to someone else and may be a little
more grumpy than average as I'm about 450 emails behind on linux-iio
and a lot more on other lists!
Jonathan
prev parent reply other threads:[~2026-07-01 0:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 14:57 [PATCH v2 0/2] iio: adc: ad7779: Remove dead code and redundant error message Moksh Panicker
2026-06-28 14:57 ` [PATCH v2 1/2] iio: adc: ad7779: Remove unused completion field Moksh Panicker
2026-06-29 23:11 ` Jonathan Cameron
2026-06-28 14:57 ` [PATCH v2 2/2] iio: adc: ad7779: Remove redundant dev_err_probe() after devm_request_irq() Moksh Panicker
2026-06-28 17:13 ` [PATCH v2 0/2] iio: adc: ad7779: Remove dead code and redundant error message Joshua Crofts
2026-06-29 23:11 ` Jonathan Cameron
2026-06-30 12:43 ` Moksh Panicker
2026-06-30 12:53 ` Joshua Crofts
2026-07-01 0:16 ` 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=20260701011635.30f6bedb@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=dlechner@baylibre.com \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mokshpanicker.7@gmail.com \
--cc=nuno.sa@analog.com \
--cc=skhan@linuxfoundation.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