[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YU7kVo2MHe7Bq1Or@unreal>
Date: Sat, 25 Sep 2021 11:56:54 +0300
From: Leon Romanovsky <leon@...nel.org>
To: David Miller <davem@...emloft.net>
Cc: kuba@...nel.org, alobakin@...me, anirudh.venkataramanan@...el.com,
aelior@...vell.com, GR-everest-linux-l2@...vell.com,
GR-QLogic-Storage-Upstream@...vell.com, irusskikh@...vell.com,
intel-wired-lan@...ts.osuosl.org, jejb@...ux.ibm.com,
jhasan@...vell.com, jeffrey.t.kirsher@...el.com,
jesse.brandeburg@...el.com, jiri@...dia.com,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
martin.petersen@...cle.com, michael.chan@...adcom.com,
michal.kalderon@...vell.com, netdev@...r.kernel.org,
sathya.perla@...adcom.com, skashyap@...vell.com,
anthony.l.nguyen@...el.com, vasundhara-v.volam@...adcom.com
Subject: Re: [PATCH net-next 0/6] Batch of devlink related fixes
On Fri, Sep 24, 2021 at 02:14:26PM +0100, David Miller wrote:
> From: Leon Romanovsky <leon@...nel.org>
> Date: Thu, 23 Sep 2021 21:12:47 +0300
>
> > From: Leon Romanovsky <leonro@...dia.com>
> >
> > Hi,
> >
> > I'm asking to apply this batch of devlink fixes to net-next and not to
> > net, because most if not all fixes are for old code or/and can be considered
> > as cleanup.
> >
> > It will cancel the need to deal with merge conflicts for my next devlink series :).
>
> ok, but just this one time.
Thanks
>
> I much rather this kind of stuff goes to net and we deal with the merge
> conflicts that arise.
I'll do.
>
> Thsnks!
Powered by blists - more mailing lists