From: Greg KH <gregkh@linuxfoundation.org>
To: Zhang Zekun <zhangzekun11@huawei.com>
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
paskripkin@gmail.com, martin@kaiser.cx, straube.linux@gmail.com,
linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
xuqiang36@huawei.com
Subject: Re: [PATCH -next] staging: r8188eu: use 'is_zero_ether_addr' to identify an empty address
Date: Mon, 4 Jul 2022 15:38:37 +0200 [thread overview]
Message-ID: <YsLtXYa4kRYEEaX/@kroah.com> (raw)
In-Reply-To: <YsLqpSGHoehauWjs@kroah.com>
On Mon, Jul 04, 2022 at 03:27:01PM +0200, Greg KH wrote:
> On Mon, Jul 04, 2022 at 12:31:40PM +0000, Zhang Zekun wrote:
> > Use 'is_zero_ether_addr' to identify an empty ethernet address, intead
> > of using 'memcpy' directly.
> >
> > Reported-by: Hulk Robot <hulkci@huawei.com>
>
> I am now just going to ignore all patch submissions with this line in it
> based on a total lack of responses by the developers using it. See
> https://lore.kernel.org/r/Yr7DQJTPrSWTOa0c@kroah.com for why.
And now just ignore patches from your domain, see:
https://lore.kernel.org/r/YsLq5vXtJgLWCqqz@kroah.com
for why (patches sent totally ignoring previous requests.)
Please work with the open source developers in your company to fix this
broken process, as it is causing more problems for me than it is worth.
greg k-h
next prev parent reply other threads:[~2022-07-04 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 12:31 [PATCH -next] staging: r8188eu: use 'is_zero_ether_addr' to identify an empty address Zhang Zekun
2022-07-04 13:27 ` Greg KH
2022-07-04 13:38 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-04 12:45 Zhang Zekun
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=YsLtXYa4kRYEEaX/@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=paskripkin@gmail.com \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@gmail.com \
--cc=xuqiang36@huawei.com \
--cc=zhangzekun11@huawei.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