From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux MediaTek <linux-mediatek@lists.infradead.org>,
Linux LEDs <linux-leds@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Shuah Khan <skhan@linuxfoundation.org>,
ChiaEn Wu <chiaen_wu@richtek.com>,
ChiYuan Huang <cy_huang@richtek.com>
Subject: Re: [PATCH 0/3] Documentation fixes for MT6370 RGB
Date: Thu, 23 Mar 2023 19:35:42 +0700 [thread overview]
Message-ID: <da9d9bca-23d5-aaa8-a815-5a9421c05a3d@gmail.com> (raw)
In-Reply-To: <20230323123156.GL2673958@google.com>
On 3/23/23 19:31, Lee Jones wrote:
>> ping
>
> a) Don't do that!
>
> b) Especually don't do that 4 days after submission!
>
> The usual expectation is 2 full weeks before submitting a [RESEND].
>
> Mark Brown says it best:
>
> "
> Please don't send content free pings and please allow a reasonable time
> for review. People get busy, go on holiday, attend conferences and so
> on so unless there is some reason for urgency (like critical bug fixes)
> please allow at least a couple of weeks for review. If there have been
> review comments then people may be waiting for those to be addressed.
>
> Sending content free pings adds to the mail volume (if they are seen at
> all) which is often the problem and since they can't be reviewed
> directly if something has gone wrong you'll have to resend the patches
> anyway, so sending again is generally a better approach though there are
> some other maintainers who like them - if in doubt look at how patches
> for the subsystem are normally handled.
> "
>
Ah! I triggered the wrong message at the wrong time. Thanks anyway!
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-03-23 12:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 7:49 [PATCH 0/3] Documentation fixes for MT6370 RGB Bagas Sanjaya
2023-03-19 7:49 ` [PATCH 1/3] Documentation: leds: Add MT6370 doc to the toctree Bagas Sanjaya
2023-03-23 15:16 ` Lee Jones
2023-03-19 7:49 ` [PATCH 2/3] Documentation: leds: MT6370: Properly wrap hw_pattern chart Bagas Sanjaya
2023-03-23 15:17 ` Lee Jones
2023-03-19 7:49 ` [PATCH 3/3] Documentation: leds: MT6370: Use bullet lists for timing variables Bagas Sanjaya
2023-03-23 15:18 ` Lee Jones
2023-03-23 5:06 ` [PATCH 0/3] Documentation fixes for MT6370 RGB Bagas Sanjaya
2023-03-23 12:31 ` Lee Jones
2023-03-23 12:35 ` Bagas Sanjaya [this message]
2023-03-23 11:08 ` Pavel Machek
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=da9d9bca-23d5-aaa8-a815-5a9421c05a3d@gmail.com \
--to=bagasdotme@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chiaen_wu@richtek.com \
--cc=corbet@lwn.net \
--cc=cy_huang@richtek.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.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