mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lin Ma" <linma@zju.edu.cn>
To: "Nikolay Aleksandrov" <razor@blackwall.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, idosch@nvidia.com, lucien.xin@gmail.com,
	liuhangbin@gmail.com, edwin.peer@broadcom.com, jiri@resnulli.us,
	md.fahad.iqbal.polash@intel.com,
	anirudh.venkataramanan@intel.com, jeffrey.t.kirsher@intel.com,
	neerav.parikh@intel.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rtnetlink: let rtnl_bridge_setlink checks IFLA_BRIDGE_MODE length
Date: Wed, 26 Jul 2023 15:49:02 +0800 (GMT+08:00)	[thread overview]
Message-ID: <7670876b.ea0b8.189912c3a92.Coremail.linma@zju.edu.cn> (raw)
In-Reply-To: <6a177bb3-0ee4-f453-695b-d9bdd441aa2c@blackwall.org>

Hi Nikolay,

> 
> Patch looks good now, you should probably remove the extra checks done
> by each driver that are now unnecessary (net-next material). As Hangbin
> commented you should target this fix at -net, with that:
> 
> Acked-by: Nikolay Aleksandrov <razor@blackwall.org>

Cool, I agree with Hangbin that another patch which removes the redundant
checks in driver is needed.

But I have a simple question. I will send this patch to net one and another
to net-next one. How can I ensure the latter one depends on the former one?
Or should I send a patch series to net-next that contains the former one :)
(I currently choose the method 2 and please let me know if I do this wrong)

Regards
Lin

  reply	other threads:[~2023-07-26  7:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25  5:57 Lin Ma
2023-07-25  7:30 ` Hangbin Liu
2023-07-25 14:30 ` Nikolay Aleksandrov
2023-07-26  7:49   ` Lin Ma [this message]
2023-07-26 15:44     ` Jakub Kicinski
2023-07-27  0:03       ` Lin Ma

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=7670876b.ea0b8.189912c3a92.Coremail.linma@zju.edu.cn \
    --to=linma@zju.edu.cn \
    --cc=anirudh.venkataramanan@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=edwin.peer@broadcom.com \
    --cc=idosch@nvidia.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=lucien.xin@gmail.com \
    --cc=md.fahad.iqbal.polash@intel.com \
    --cc=neerav.parikh@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.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
all inboxes | Powered by JetHome®