From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: "Franziska Näpelt" <franziska.naepelt@googlemail.com>,
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: [v4 1/3] staging: rtl8723bs: Fix space issues
Date: Mon, 24 Jul 2023 11:22:49 +0200 [thread overview]
Message-ID: <2023072440-dimple-slicer-3fd7@gregkh> (raw)
In-Reply-To: <c6374bc6-2a56-23b0-6ef9-def092aaed4a@web.de>
On Mon, Jul 24, 2023 at 10:44:15AM +0200, Markus Elfring wrote:
> > Everyone please note, Markus has been banned from most kernel mailing lists,
>
> I hope that this ban can still be reconsidered.
At this point in time, sorry, but no.
next prev parent reply other threads:[~2023-07-24 9:23 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
2023-07-24 8:00 ` Greg Kroah-Hartman
2023-07-24 8:44 ` [v4 " Markus Elfring
2023-07-24 9:22 ` Greg Kroah-Hartman [this message]
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=2023072440-dimple-slicer-3fd7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Markus.Elfring@web.de \
--cc=dan.carpenter@linaro.org \
--cc=eperi1024@gmail.com \
--cc=franziska.naepelt@googlemail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.