Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Tomasz_Mo=C5=84_=3Ctomasz=2Emon=40camlingroup=2Ecom=3E?=@ci.codeaurora.org
Cc: mkubecek@suse.cz, netdev@vger.kernel.org, andrew@lunn.ch,
	k.drobinski@camlintechnologies.com
Subject: Re: [PATCH ethtool v2] ethtool: fix EEPROM byte write
Date: Sun, 21 Aug 2022 23:20:14 +0000	[thread overview]
Message-ID: <166112401428.18015.17121968963411126665.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220819101049.1939033-1-tomasz.mon@camlingroup.com>

Hello:

This patch was applied to ethtool/ethtool.git (master)
by Michal Kubecek <mkubecek@suse.cz>:

On Fri, 19 Aug 2022 12:10:49 +0200 you wrote:
> ethtool since version 1.8 supports EEPROM byte write:
>   # ethtool -E DEVNAME [ magic N ] [ offset N ] [ value N ]
> 
> ethtool 2.6.33 added EEPROM block write:
>   # ethtool -E ethX [ magic N ] [ offset N ] [ length N ] [ value N ]
> 
> EEPROM block write introduced in 2.6.33 is backwards compatible, i.e.
> when value is specified the length is forced to 1 (commandline length
> value is ignored).
> 
> [...]

Here is the summary with links:
  - [ethtool,v2] ethtool: fix EEPROM byte write
    https://git.kernel.org/pub/scm/network/ethtool/ethtool.git/commit/?id=95a8d982f159

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



  reply	other threads:[~2022-08-21 23:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 10:10 [PATCH ethtool v2] ethtool: fix EEPROM byte write Tomasz Moń
2022-08-21 23:20 ` patchwork-bot+netdevbpf [this message]
2022-08-21 23:28 ` Michal Kubecek

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=166112401428.18015.17121968963411126665.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?q?Tomasz_Mo=C5=84_=3Ctomasz=2Emon=40camlingroup=2Ecom=3E?=@ci.codeaurora.org \
    --cc=andrew@lunn.ch \
    --cc=k.drobinski@camlintechnologies.com \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox