linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Jilin Yuan <yuanjilin@cdjrlc.com>,
	frowand.list@gmail.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: device: fix repeated words in comments
Date: Tue, 27 Sep 2022 09:07:15 -0500	[thread overview]
Message-ID: <CAL_JsqJcs9N9m8ymQRWx3VV=7m2959FOrcuTpU6JDRuMwUeX9Q@mail.gmail.com> (raw)
In-Reply-To: <8821ae25-eb20-b673-6d57-fb2cc03d9726@gmail.com>

On Tue, Sep 27, 2022 at 7:47 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> On 9/27/22 19:29, Rob Herring wrote:
> >> Hi Rob,
> >>
> >> Some reviewers sent comments for similar patches from @cdjrlc.com
> >> people (including myself at [1]), with some of them requesting changes.
> >> However, there are never any responses to these reviews from @cdjrlc.com
> >> people, just like ZTE developers sending through cgel.zte ignored
> >> review comments [2] (try searching `f:"cdjrlc.com" AND s:"Re:"`, it returns
> >> nothing for now).
> >
> > I can't decide whether to fix it correctly myself or leave it to see
> > how many times I can get the same patch. :)
> >
>
> Hi Rob,
>
> I'm not talking about whether this patch should be picked up or not, but
> rather I'm pointing out the ignoring review behavior of @cdjrlc.com people.

Yes, I get that. Not responding seems to be a growing behavior not
just on these trivial type patches. (Though replying with 'ok' to
every review comment is equally annoying.) I suppose there could be
some filtering happening such that replies are never received.

Rob

      reply	other threads:[~2022-09-27 14:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18  9:49 [PATCH] of: device: fix repeated words in comments Jilin Yuan
2022-09-26 18:58 ` Rob Herring
2022-09-27  2:04   ` Bagas Sanjaya
2022-09-27 12:29     ` Rob Herring
2022-09-27 12:47       ` Bagas Sanjaya
2022-09-27 14:07         ` Rob Herring [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='CAL_JsqJcs9N9m8ymQRWx3VV=7m2959FOrcuTpU6JDRuMwUeX9Q@mail.gmail.com' \
    --to=robh@kernel.org \
    --cc=bagasdotme@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuanjilin@cdjrlc.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).