From: Jakub Kicinski <kuba@kernel.org>
To: Hayes Wang <hayeswang@realtek.com>,
Grant Grundler <grundler@chromium.org>
Cc: Oliver Neukum <oliver@neukum.org>,
"David S. Miller" <davem@davemloft.net>,
nic_swsd <nic_swsd@realtek.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] net: usb: cdc_ncm: don't spew notifications
Date: Wed, 20 Jan 2021 09:04:38 -0800 [thread overview]
Message-ID: <20210120090438.0f5bba6e@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <0a5e1dad04494f16869b44b8457f0980@realtek.com>
On Wed, 20 Jan 2021 03:38:32 +0000 Hayes Wang wrote:
> Grant Grundler <grundler@chromium.org>
> > Sent: Wednesday, January 20, 2021 9:12 AM
> > Subject: [PATCH net] net: usb: cdc_ncm: don't spew notifications
> >
> > RTL8156 sends notifications about every 32ms.
> > Only display/log notifications when something changes.
> >
> > This issue has been reported by others:
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832472
> > https://lkml.org/lkml/2020/8/27/1083
> >
> > Chrome OS cannot support RTL8156 until this is fixed.
> >
> > Signed-off-by: Grant Grundler <grundler@chromium.org>
>
> Reviewed-by: Hayes Wang <hayeswang@realtek.com>
Applied, thanks!
net should be merged back into net-next by the end of the day, so
if the other patches depend on this one to apply cleanly please keep
an eye and post after that happens. If there is no conflict you can
just post them with [PATCH net-next] now.
next prev parent reply other threads:[~2021-01-20 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 1:12 [PATCH net] net: usb: cdc_ncm: don't spew notifications Grant Grundler
2021-01-20 3:38 ` Hayes Wang
2021-01-20 17:04 ` Jakub Kicinski [this message]
2021-03-04 19:10 ` Grant Grundler
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=20210120090438.0f5bba6e@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=grundler@chromium.org \
--cc=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=oliver@neukum.org \
/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).