[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zs6Z3CGh0aTOrXT4@Laptop-X1>
Date: Wed, 28 Aug 2024 11:30:36 +0800
From: Hangbin Liu <liuhangbin@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, Jay Vosburgh <j.vosburgh@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com>,
Nikolay Aleksandrov <razor@...ckwall.org>,
Tariq Toukan <tariqt@...dia.com>, Jianbo Liu <jianbol@...dia.com>,
Sabrina Dubroca <sd@...asysnail.net>,
Simon Horman <horms@...nel.org>,
Steffen Klassert <steffen.klassert@...unet.com>
Subject: Re: [PATCHv4 net-next 1/3] bonding: add common function to check
ipsec device
On Tue, Aug 27, 2024 at 07:28:01PM -0700, Jakub Kicinski wrote:
>
> Yes, but still a bit too much info in the "short description"
> how about:
>
> /**
> * bond_ipsec_dev - Get active device for IPsec offload
> * @xs: pointer to transformer state struct
> *
> * Context: caller must hold rcu_read_lock.
> *
> * Return the device for ipsec offload, or NULL if not exist.
> **/
OK, thanks for the update :)
>
> > BTW, The patch now has conflicts with latest net-next, I can do a rebase if
> > you want.
>
> net or net-next? the patches from nvidia went into net.
> If it conflicts with net-next please rebase.
It conflicts with Nikolay's bond xfrm fixes, which already in net-next.
I will do a rebase.
Thanks
Hangbin
> If it conflicts with net -- could you wait with repost
> until after the net PR to Linus? And then rebase & post?
Powered by blists - more mailing lists