From: Coiby Xu <coiby.xu@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 01/15] iio: accel: remove unnecessary CONFIG_PM_SLEEP
Date: Fri, 30 Oct 2020 22:34:10 +0800 [thread overview]
Message-ID: <20201030143410.pbixjo2cllhd27zp@Rk> (raw)
In-Reply-To: <CAHp75Vc829u6XPPA+eE=_AFZSPF+yVqT7nUXxtzkwx7-xLLrCg@mail.gmail.com>
On Thu, Oct 29, 2020 at 07:06:40PM +0200, Andy Shevchenko wrote:
>On Thu, Oct 29, 2020 at 4:42 PM Jonathan Cameron <jic23@kernel.org> wrote:
>> On Thu, 29 Oct 2020 15:48:56 +0800
>> Coiby Xu <coiby.xu@gmail.com> wrote:
>
>> Please put a cover letter on your next series explaining the context.
>> In this particular case some of the replies you have gotten are
>> general at it is a lot easier to find these sorts of things via
>> replying to the cover letter.
>
>Looking at the number of duplicate messages I would suggest that one
>needs to go through documentation on how to use git format-patch and
>git send-email.
>
Thank you for the suggestion! Actually it's a tree-wide change and it
seems the kernel community prefer individual patches or series for
subsystems having the same maintainer over a huge patch set so I wrote
some scripts to automate the process. That's why you see ~50 emails
with almost the same commit message. The only difference of these
commit messages is the name of PM macro.
>--
>With Best Regards,
>Andy Shevchenko
--
Best regards,
Coiby
next prev parent reply other threads:[~2020-10-30 14:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 7:48 [PATCH 01/15] iio: accel: remove unnecessary CONFIG_PM_SLEEP Coiby Xu
2020-10-29 7:48 ` [PATCH 02/15] " Coiby Xu
2020-10-29 7:48 ` [PATCH 03/15] " Coiby Xu
2020-10-29 7:48 ` [PATCH 04/15] " Coiby Xu
2020-10-29 7:49 ` [PATCH 05/15] " Coiby Xu
2020-10-29 11:57 ` Andy Shevchenko
2020-10-29 14:41 ` Coiby Xu
2020-10-29 7:49 ` [PATCH 06/15] " Coiby Xu
2020-10-29 7:49 ` [PATCH 07/15] iio: ssp: " Coiby Xu
2020-10-29 7:49 ` [PATCH 08/15] iio: magnetometer: mmc35240: " Coiby Xu
2020-10-29 7:49 ` [PATCH 09/15] iio: adc: palmas_gpadc: " Coiby Xu
2020-10-29 7:49 ` [PATCH 10/15] iio: adc: stm32: " Coiby Xu
2020-10-29 7:49 ` Coiby Xu
2020-10-29 11:31 ` Fabrice Gasnier
2020-10-29 11:31 ` Fabrice Gasnier
2020-10-29 7:49 ` [PATCH 11/15] iio: adc: at91_adc: " Coiby Xu
2020-10-29 7:49 ` Coiby Xu
2020-10-29 7:49 ` [PATCH 12/15] iio: imu: kmx61: " Coiby Xu
2020-10-29 7:49 ` [PATCH 13/15] iio: light: us5182d: " Coiby Xu
2020-10-29 7:49 ` [PATCH 14/15] iio: light: " Coiby Xu
2020-10-29 7:49 ` [PATCH 15/15] iio: proximity: " Coiby Xu
2020-10-29 14:40 ` [PATCH 01/15] iio: accel: " Jonathan Cameron
2020-10-29 14:43 ` Coiby Xu
2020-10-29 17:06 ` Andy Shevchenko
2020-10-30 14:34 ` Coiby Xu [this message]
2020-10-31 11:05 ` Jonathan Cameron
2020-10-31 22:47 ` Coiby Xu
2020-11-01 17:20 ` 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=20201030143410.pbixjo2cllhd27zp@Rk \
--to=coiby.xu@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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.