From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, jeffrey.t.kirsher@intel.com,
timur@kernel.org, intel-wired-lan@lists.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: Demote MTU change prints to debug
Date: Thu, 07 Nov 2019 20:01:31 -0800 (PST) [thread overview]
Message-ID: <20191107.200131.396855107998573876.davem@davemloft.net> (raw)
In-Reply-To: <20191107223537.23440-1-f.fainelli@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Thu, 7 Nov 2019 14:35:35 -0800
> This patch series demotes several drivers that printed MTU change and
> could therefore spam the kernel console if one has a test that it's all
> about testing the values. Intel drivers were not also particularly
> consistent in how they printed the same message, so now they are.
Series applied, thanks Florian.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next 0/2] net: Demote MTU change prints to debug
Date: Thu, 07 Nov 2019 20:01:31 -0800 (PST) [thread overview]
Message-ID: <20191107.200131.396855107998573876.davem@davemloft.net> (raw)
In-Reply-To: <20191107223537.23440-1-f.fainelli@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Thu, 7 Nov 2019 14:35:35 -0800
> This patch series demotes several drivers that printed MTU change and
> could therefore spam the kernel console if one has a test that it's all
> about testing the values. Intel drivers were not also particularly
> consistent in how they printed the same message, so now they are.
Series applied, thanks Florian.
next prev parent reply other threads:[~2019-11-08 4:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 22:35 [PATCH net-next 0/2] net: Demote MTU change prints to debug Florian Fainelli
2019-11-07 22:35 ` [Intel-wired-lan] " Florian Fainelli
2019-11-07 22:35 ` [PATCH net-next 1/2] net: ethernet: intel: " Florian Fainelli
2019-11-07 22:35 ` [Intel-wired-lan] " Florian Fainelli
2019-11-07 22:52 ` Jeff Kirsher
2019-11-07 22:52 ` [Intel-wired-lan] " Jeff Kirsher
2019-11-07 22:35 ` [PATCH net-next 2/2] net: qcom/emac: Demote MTU change print " Florian Fainelli
2019-11-07 22:35 ` [Intel-wired-lan] " Florian Fainelli
2019-11-08 2:57 ` Timur Tabi
2019-11-08 2:57 ` [Intel-wired-lan] " Timur Tabi
2019-11-08 4:01 ` David Miller [this message]
2019-11-08 4:01 ` [Intel-wired-lan] [PATCH net-next 0/2] net: Demote MTU change prints " David Miller
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=20191107.200131.396855107998573876.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=timur@kernel.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 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.