From: patchwork-bot+netdevbpf@kernel.org
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: qiangqing.zhang@nxp.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: fec: don't reset irq coalesce settings to defaults on "ip link up"
Date: Fri, 25 Nov 2022 09:40:16 +0000 [thread overview]
Message-ID: <166936921675.2800.4020168798324451407.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221123133853.1822415-1-linux@rasmusvillemoes.dk>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 23 Nov 2022 14:38:52 +0100 you wrote:
> Currently, when a FEC device is brought up, the irq coalesce settings
> are reset to their default values (1000us, 200 frames). That's
> unexpected, and breaks for example use of an appropriate .link file to
> make systemd-udev apply the desired
> settings (https://www.freedesktop.org/software/systemd/man/systemd.link.html),
> or any other method that would do a one-time setup during early boot.
>
> [...]
Here is the summary with links:
- net: fec: don't reset irq coalesce settings to defaults on "ip link up"
https://git.kernel.org/netdev/net/c/df727d4547de
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-11-25 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 13:38 [PATCH] net: fec: don't reset irq coalesce settings to defaults on "ip link up" Rasmus Villemoes
2022-11-23 18:07 ` Andrew Lunn
2022-11-25 9:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-05 7:15 Greg Ungerer
2022-12-05 8:44 ` Rasmus Villemoes
2022-12-05 13:15 ` Greg Ungerer
2022-12-05 13:19 ` Andrew Lunn
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=166936921675.2800.4020168798324451407.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qiangqing.zhang@nxp.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