netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5 next] net: vertexcom: mse102x: Use ETH_ZLEN
Date: Wed, 28 Aug 2024 15:40:53 +0100	[thread overview]
Message-ID: <20240828144053.GM1368797@kernel.org> (raw)
In-Reply-To: <20240827191000.3244-6-wahrenst@gmx.net>

On Tue, Aug 27, 2024 at 09:10:00PM +0200, Stefan Wahren wrote:
> There is already a define for minimum Ethernet frame length without FCS.
> So used this instead of the magic number.
> 
> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>

Reviewed-by: Simon Horman <horms@kernel.org>


  reply	other threads:[~2024-08-28 14:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27 19:09 [PATCH 0/5 next] net: vertexcom: mse102x: Minor clean-ups Stefan Wahren
2024-08-27 19:09 ` [PATCH 1/5 next] net: vertexcom: mse102x: Use DEFINE_SIMPLE_DEV_PM_OPS Stefan Wahren
2024-08-28 14:39   ` Simon Horman
2024-08-27 19:09 ` [PATCH 2/5 next] net: vertexcom: mse102x: Silence TX timeout Stefan Wahren
2024-08-28 14:40   ` Simon Horman
2024-08-27 19:09 ` [PATCH 3/5 next] net: vertexcom: mse102x: Fix random MAC address log Stefan Wahren
2024-08-28 14:40   ` Simon Horman
2024-08-27 19:09 ` [PATCH 4/5 next] net: vertexcom: mse102x: Drop log message on remove Stefan Wahren
2024-08-28 14:40   ` Simon Horman
2024-08-27 19:10 ` [PATCH 5/5 next] net: vertexcom: mse102x: Use ETH_ZLEN Stefan Wahren
2024-08-28 14:40   ` Simon Horman [this message]
2024-08-29 21:31 ` [PATCH 0/5 next] net: vertexcom: mse102x: Minor clean-ups Jakub Kicinski

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=20240828144053.GM1368797@kernel.org \
    --to=horms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wahrenst@gmx.net \
    /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).