From: Simon Horman <horms@kernel.org>
To: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
Cc: netdev@vger.kernel.org,
Horatiu Vultur <horatiu.vultur@microchip.com>,
UNGLinuxDriver@microchip.com,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] net: lan966x: cleanup lan966x_tc_flower_handler_control_usage()
Date: Tue, 23 Apr 2024 15:00:48 +0100 [thread overview]
Message-ID: <20240423140048.GU42092@kernel.org> (raw)
In-Reply-To: <20240423102720.228728-1-ast@fiberby.net>
On Tue, Apr 23, 2024 at 10:27:17AM +0000, Asbjørn Sloth Tønnesen wrote:
> Define extack locally, to reduce line lengths and future users.
>
> Rename goto, as the error message is specific to the fragment flags.
>
> Only compile-tested.
>
> Signed-off-by: Asbjørn Sloth Tønnesen <ast@fiberby.net>
Hi Asbjørn,
This patch-set did not apply to net-next at the time it was posted
(although it does now), so it will need to be reposted.
Also, please consider providing a cover-letter for patch-sets with
more than one (but not just one) patch.
--
pw-bot: changes-requested
next prev parent reply other threads:[~2024-04-23 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 10:27 [PATCH net-next 1/2] net: lan966x: cleanup lan966x_tc_flower_handler_control_usage() Asbjørn Sloth Tønnesen
2024-04-23 10:27 ` [PATCH net-next 2/2] net: lan966x: flower: check for unsupported control flags Asbjørn Sloth Tønnesen
2024-04-23 11:21 ` [PATCH net-next 1/2] net: lan966x: cleanup lan966x_tc_flower_handler_control_usage() Jiri Pirko
2024-04-23 14:00 ` Simon Horman [this message]
2024-04-23 14:58 ` Asbjørn Sloth Tønnesen
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=20240423140048.GU42092@kernel.org \
--to=horms@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=ast@fiberby.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.