Linux IIO development
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Dimitri Fedrau <dima.fedrau@gmail.com>,
	linux-iio@vger.kernel.org, kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Hepp <andrew.hepp@ahepp.dev>,
	Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Subject: Re: [PATCH v2 1/2] iio: temperature: mcp9600: Provide index for both channels
Date: Fri, 17 May 2024 17:30:57 +0200	[thread overview]
Message-ID: <d313e351-6697-4d4f-8950-2b784a2de9f0@web.de> (raw)
In-Reply-To: <20240517081050.168698-2-dima.fedrau@gmail.com>

I suggest to reconsider the distribution of email addresses over recipient lists
once more.


…
> We provide an index for …

Please improve the change description with an imperative wording.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9#n94

Regards,
Markus

  reply	other threads:[~2024-05-17 15:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17  8:10 [PATCH v2 0/2] Add threshold events support Dimitri Fedrau
2024-05-17  8:10 ` [PATCH v2 1/2] iio: temperature: mcp9600: Provide index for both channels Dimitri Fedrau
2024-05-17 15:30   ` Markus Elfring [this message]
2024-05-19 16:14   ` Jonathan Cameron
2024-05-19 20:32     ` Dimitri Fedrau
2024-05-20 12:17       ` Jonathan Cameron
2024-05-21  2:28     ` Andrew Hepp
2024-05-23 11:21       ` Dimitri Fedrau
2024-05-17  8:10 ` [PATCH v2 2/2] iio: temperature: mcp9600: add threshold events support Dimitri Fedrau
2024-05-19 16:42   ` Jonathan Cameron
2024-05-19 21:00     ` Dimitri Fedrau
2024-05-20 12:18       ` Jonathan Cameron
2024-05-23 11:14         ` Dimitri Fedrau
2024-05-17 13:28 ` [PATCH v2 0/2] Add " Jonathan Cameron

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=d313e351-6697-4d4f-8950-2b784a2de9f0@web.de \
    --to=markus.elfring@web.de \
    --cc=andrew.hepp@ahepp.dev \
    --cc=dima.fedrau@gmail.com \
    --cc=jic23@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.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