From: Greg KH <greg@kroah.com>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>
Cc: Ian Pilcher <arequipeno@gmail.com>, kernelnewbies@kernelnewbies.org
Subject: Re: When reviewers stop responding
Date: Wed, 22 Jun 2022 11:34:28 +0200 [thread overview]
Message-ID: <YrLiJLcEN+HR7qJz@kroah.com> (raw)
In-Reply-To: <9fa37c18-e6a1-f33d-3f58-1bd4490fe767@gmail.com>
On Wed, Jun 22, 2022 at 06:20:04AM +0200, Philipp Hortmann wrote:
> On 6/7/22 19:23, Greg KH wrote:
> > And again, please help review code, otherwise you are just asking others
> > to do work for you, which if you think about it, could be construed as a
> > bit selfish, and I don't think you mean it to be.
>
> Hi Greg,
>
> this applies to me. I promise to improve. But this topic is not enough
> advertised. Everywhere information about patches can be found. But how to do
> a correct Reviewed-by: or Tested-by: is not so good documented.
>
> I bought hardware to improve and did one "Tested-by:" of the patch:
>
> [PATCH v2 0/5] Fixed some coding style issues and spelling
> from Chang Yu <marcus.yu.56@gmail.com>
>
> https://lore.kernel.org/linux-staging/91c9a0de-76f8-37fb-31b4-4401a6e35d48@gmail.com/T/#t
>
> Did I do something wrong or was I just unlucky?
>
> Is 24 hours quick enough response?
Sometimes, yes, it is. Other times I get to patches quicker than that
as I batch them up and process them once or twice a week. You just got
unlucky and reviewed it after I had applied the changes, but that was
not the case for your other series you reviewed today.
thanks for the review, it's always appreciated.
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2022-06-22 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 19:55 When reviewers stop responding Ian Pilcher
2021-11-19 7:08 ` Greg KH
2022-06-07 17:19 ` Ian Pilcher
2022-06-07 17:23 ` Greg KH
2022-06-22 4:20 ` Philipp Hortmann
2022-06-22 9:34 ` Greg KH [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=YrLiJLcEN+HR7qJz@kroah.com \
--to=greg@kroah.com \
--cc=arequipeno@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=philipp.g.hortmann@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;
as well as URLs for NNTP newsgroup(s).