mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
To: Simon Horman <horms@kernel.org>
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 14:58:54 +0000	[thread overview]
Message-ID: <883a41cc-58b2-475b-a247-b45f69c7f24b@fiberby.net> (raw)
In-Reply-To: <20240423140048.GU42092@kernel.org>

Hi Simon,

On 4/23/24 2:00 PM, Simon Horman wrote:
> 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.

Weird, patchwork incorrectly matched up the two series. I had
rebased shortly before posting (net-next was at 077633afe07f4).

The 4 emails and their Subject, Message-ID and In-Reply-To:

Subject: [PATCH net-next 1/2] net: sparx5: flower: cleanup sparx5_tc_flower_handler_control_usage()
Message-ID: <20240423102728.228765-1-ast@fiberby.net>  (A)

Subject: [PATCH net-next 2/2] net: sparx5: flower: check for unsupported control flags
Message-ID: <20240423102728.228765-2-ast@fiberby.net>  (B)
In-Reply-To: <20240423102728.228765-1-ast@fiberby.net> (A)

Subject: [PATCH net-next 1/2] net: lan966x: cleanup lan966x_tc_flower_handler_control_usage()
Message-ID: <20240423102720.228728-1-ast@fiberby.net>  (C)

Subject: [PATCH net-next 2/2] net: lan966x: flower: check for unsupported control flags
Message-ID: <20240423102720.228728-2-ast@fiberby.net>  (D)
In-Reply-To: <20240423102720.228728-1-ast@fiberby.net> (C)

Patchwork have two series A+D and C+B, instead of A+B and C+D.

> Also, please consider providing a cover-letter for patch-sets with
> more than one (but not just one) patch.

Sure, will do. Didn't know if it was appreciated for so small series,
anyway v2 will have more patches, after splitting this patch up.

-- 
Best regards
Asbjørn Sloth Tønnesen
Network Engineer
Fiberby - AS42541

      reply	other threads:[~2024-04-23 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 10:27 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
2024-04-23 14:58   ` Asbjørn Sloth Tønnesen [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=883a41cc-58b2-475b-a247-b45f69c7f24b@fiberby.net \
    --to=ast@fiberby.net \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=horms@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®