From: Nam Cao <namcaov@gmail.com>
To: "Franziska Näpelt" <franziska.naepelt@googlemail.com>
Cc: Markus Elfring <Markus.Elfring@web.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, kernel-janitors@vger.kernel.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: [PATCH v4 1/3] staging: rtl8723bs: Fix space issues
Date: Sun, 23 Jul 2023 20:55:35 +0200 [thread overview]
Message-ID: <ZL13p4tSQAx6cx8E@nam-dell> (raw)
In-Reply-To: <ZL11kmTYFXMwrYww@nam-dell>
On Sun, Jul 23, 2023 at 08:46:42PM +0200, Nam Cao wrote:
> On Sun, Jul 23, 2023 at 07:44:44PM +0200, Franziska Näpelt wrote:
> > Hi Markus,
> >
> > Am So., 23. Juli 2023 um 08:19 Uhr schrieb Markus Elfring
> > <Markus.Elfring@web.de>:
> > >
> > > > Am I supposed to adjust something here?
> > >
> > > There are possibilities remaining to handle recurring communication difficulties
> > > in more constructive ways for some hints.
> > >
> > >
> > > > As far as I understood, I can ignore the comments from Markus, correct?
> > >
> > > Would the provided technical information be taken better into account
> > > if it would be presented by any other contributors?
> >
> > That's not my point, I appreciate feedback from anybody, absolutely no question
> > on that. I'm just struggling to know what I'm supposed to do when the maintainer
> > is saying somebody's comments are not helpful.
>
> I would wait some more. Greg is probably just too busy to take your patches at
> the moment.
Don't let that slows you down though, work on other patches in the mean time if
you would like to.
next prev parent reply other threads:[~2023-07-23 18:55 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 [this message]
2023-07-24 7:40 ` [ " Markus Elfring
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=ZL13p4tSQAx6cx8E@nam-dell \
--to=namcaov@gmail.com \
--cc=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