All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: pavan.chebbi@broadcom.com, mchan@broadcom.com, kuba@kernel.org,
	davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
	andrew@lunn.ch, linux@armlinux.org.uk, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tg3: copy only needed fields from userspace-provided EEE data
Date: Wed, 21 Feb 2024 11:20:26 +0000	[thread overview]
Message-ID: <170851442684.9417.11313982323041176544.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <59bd00bf-7263-43d9-a438-c2930bfdb91c@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Sun, 18 Feb 2024 15:49:55 +0100 you wrote:
> The current code overwrites fields in tp->eee with unchecked data from
> edata, e.g. the bitmap with supported modes. ethtool properly returns
> the received data from get_eee() call, but we have no guarantee that
> other users of the ioctl set_eee() interface behave properly too.
> Therefore copy only fields which are actually needed.
> 
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> 
> [...]

Here is the summary with links:
  - [net-next] tg3: copy only needed fields from userspace-provided EEE data
    https://git.kernel.org/netdev/net-next/c/8306ee08c0ff

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-02-21 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18 14:49 [PATCH net-next] tg3: copy only needed fields from userspace-provided EEE data Heiner Kallweit
2024-02-18 17:04 ` Andrew Lunn
2024-02-18 17:31   ` Heiner Kallweit
2024-02-21 11:20 ` patchwork-bot+netdevbpf [this message]

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=170851442684.9417.11313982323041176544.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mchan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pavan.chebbi@broadcom.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.