From: Markus Elfring <Markus.Elfring@web.de>
To: "Franziska Näpelt" <franziska.naepelt@googlemail.com>,
linux-staging@lists.linux.dev, kernel-janitors@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Emily Peri <eperi1024@gmail.com>, Guo Zihua <guozihua@huawei.com>,
Hans de Goede <hdegoede@redhat.com>,
Kang Minchul <tegongkang@gmail.com>,
Philipp Hortmann <philipp.g.hortmann@gmail.com>,
Veerendranath Jakkam <quic_vjakkam@quicinc.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ v4 1/3] staging: rtl8723bs: Fix space issues
Date: Mon, 24 Jul 2023 09:40:04 +0200 [thread overview]
Message-ID: <67b16362-aace-28e3-6776-aefdeab0f183@web.de> (raw)
In-Reply-To: <CAAUT3iPUaNRUyvqP1O97M0AmKri7Ghc06ku4TS6vcHQ=Sb4ycg@mail.gmail.com>
> I'm just struggling to know what I'm supposed to do when the maintainer
> is saying somebody's comments are not helpful.
I suggest to take another look at the circumstances and corresponding
background information.
I would appreciate if the involved communication factors can be reconsidered
any more.
Which impressions do you get from my previous contributions so far?
Example:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/?qt=grep&q=Elfring
I imagine that my recent review comments can eventually influence
the “beautification” another bit for subsequent patches.
Regards,
Markus
next prev parent reply other threads:[~2023-07-24 7:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 10:22 [PATCH v4 0/3] staging: rtl8723bs: Fix some checkpatch issues Franziska Naepelt
2023-07-01 10:25 ` [PATCH v4 1/3] staging: rtl8723bs: Fix space issues Franziska Naepelt
2023-07-01 14:43 ` Markus Elfring
2023-07-01 15:00 ` Greg Kroah-Hartman
2023-07-01 15:34 ` Markus Elfring
2023-07-22 22:29 ` Franziska Näpelt
2023-07-23 6:18 ` Markus Elfring
2023-07-23 17:44 ` Franziska Näpelt
2023-07-23 18:46 ` Nam Cao
2023-07-23 18:55 ` Nam Cao
2023-07-24 7:40 ` Markus Elfring [this message]
2023-07-24 8:00 ` [ " Greg Kroah-Hartman
2023-07-24 8:44 ` [v4 " Markus Elfring
2023-07-24 9:22 ` Greg Kroah-Hartman
2023-07-24 6:28 ` [PATCH v4 " Dan Carpenter
2023-07-24 8:07 ` [v4 " Markus Elfring
2023-07-01 10:25 ` [PATCH v4 2/3] staging: rtl8723bs: Fix alignment open parenthesis Franziska Naepelt
2023-07-01 10:26 ` [PATCH v4 3/3] staging: rtl8723bs: Fix remaining blank line issue Franziska Naepelt
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=67b16362-aace-28e3-6776-aefdeab0f183@web.de \
--to=markus.elfring@web.de \
--cc=dan.carpenter@linaro.org \
--cc=eperi1024@gmail.com \
--cc=franziska.naepelt@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=guozihua@huawei.com \
--cc=hdegoede@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@gmail.com \
--cc=quic_vjakkam@quicinc.com \
--cc=tegongkang@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