From: Mark Brown <broonie@kernel.org>
To: Yinbo Zhu <zhuyinbo@loongson.cn>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Jianmin Lv <lvjianmin@loongson.cn>,
wanghongliang@loongson.cn, Liu Peibao <liupeibao@loongson.cn>,
loongson-kernel@lists.loongnix.cn,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v13 2/2] spi: loongson: add bus driver for the loongson spi controller
Date: Fri, 28 Jul 2023 13:31:01 +0100 [thread overview]
Message-ID: <67b74e69-f660-43e3-831f-47dbe0fea6fa@sirena.org.uk> (raw)
In-Reply-To: <8ad55123-fbf2-2b0f-faba-f71bb89c7fb1@loongson.cn>
[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]
On Fri, Jul 28, 2023 at 11:36:48AM +0800, Yinbo Zhu wrote:
> 在 2023/7/27 下午7:37, Mark Brown 写道:
> > On Thu, Jul 27, 2023 at 11:09:16AM +0800, Yinbo Zhu wrote:
> > > Friendly ping ?
> > 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.
> Sorry, my community experience is poor. How many weeks does the
> community usually take to review ? and this time that I waited for six
> weeks and then ping.
The delay here is probably fine - the above is a form letter that I send
whenever people ping so it tries to cover all eventualities. How long
to leave things depends a bit on what the change is, an urgent bugfix is
going to be different from a spelling fix in a comment.
> > 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.
> Sorry, I don't got it, that free ping usually only needs to be sent to
> the subsystem maintainer?
> Not recommended to use free ping? or resend the same patch. If the
> patch does not need to be modified, does it require sending the same
> patch ? And the version number remains the same?
I'm saying it's generally better to ping by resending the patch.
Typically keeping the same version number makes sense when doing that -
people normally say [PATCH RESEND vN] in the subject line.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-28 12:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 7:58 [PATCH v13 0/2] spi: loongson: add bus driver for the loongson spi Yinbo Zhu
2023-06-13 7:58 ` [PATCH v13 1/2] spi: dt-bindings: add " Yinbo Zhu
2023-06-13 7:58 ` [PATCH v13 2/2] spi: loongson: add bus driver for the loongson spi controller Yinbo Zhu
2023-06-13 13:03 ` Andy Shevchenko
2023-06-14 2:03 ` zhuyinbo
2023-07-27 3:09 ` Yinbo Zhu
2023-07-27 11:37 ` Mark Brown
2023-07-28 3:36 ` Yinbo Zhu
2023-07-28 12:31 ` Mark Brown [this message]
2023-07-31 6:07 ` Yinbo Zhu
2023-07-31 19:57 ` [PATCH v13 0/2] spi: loongson: add bus driver for the loongson spi Mark Brown
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=67b74e69-f660-43e3-831f-47dbe0fea6fa@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=liupeibao@loongson.cn \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=lvjianmin@loongson.cn \
--cc=wanghongliang@loongson.cn \
--cc=zhuyinbo@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).