From: Leon Romanovsky <leon@kernel.org>
To: David Miller <davem@davemloft.net>
Cc: kuba@kernel.org, alobakin@pm.me,
anirudh.venkataramanan@intel.com, aelior@marvell.com,
GR-everest-linux-l2@marvell.com,
GR-QLogic-Storage-Upstream@marvell.com, irusskikh@marvell.com,
intel-wired-lan@lists.osuosl.org, jejb@linux.ibm.com,
jhasan@marvell.com, jeffrey.t.kirsher@intel.com,
jesse.brandeburg@intel.com, jiri@nvidia.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
martin.petersen@oracle.com, michael.chan@broadcom.com,
michal.kalderon@marvell.com, netdev@vger.kernel.org,
sathya.perla@broadcom.com, skashyap@marvell.com,
anthony.l.nguyen@intel.com, vasundhara-v.volam@broadcom.com
Subject: Re: [PATCH net-next 0/6] Batch of devlink related fixes
Date: Sat, 25 Sep 2021 11:56:54 +0300 [thread overview]
Message-ID: <YU7kVo2MHe7Bq1Or@unreal> (raw)
In-Reply-To: <20210924.141426.1767931642845359040.davem@davemloft.net>
On Fri, Sep 24, 2021 at 02:14:26PM +0100, David Miller wrote:
> From: Leon Romanovsky <leon@kernel.org>
> Date: Thu, 23 Sep 2021 21:12:47 +0300
>
> > From: Leon Romanovsky <leonro@nvidia.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!
next prev parent reply other threads:[~2021-09-25 8:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 18:12 [PATCH net-next 0/6] Batch of devlink related fixes Leon Romanovsky
2021-09-23 18:12 ` [PATCH net-next 1/6] bnxt_en: Check devlink allocation and registration status Leon Romanovsky
2021-09-23 21:11 ` Edwin Peer
2021-09-23 23:11 ` Leon Romanovsky
2021-09-24 1:39 ` Jakub Kicinski
2021-09-24 17:20 ` Edwin Peer
2021-09-25 10:01 ` Leon Romanovsky
2021-09-23 18:12 ` [PATCH net-next 2/6] bnxt_en: Properly remove port parameter support Leon Romanovsky
2021-09-23 21:23 ` Edwin Peer
2021-09-23 18:12 ` [PATCH net-next 3/6] devlink: Delete not used port parameters APIs Leon Romanovsky
2021-09-23 18:12 ` [PATCH net-next 4/6] devlink: Remove single line function obfuscations Leon Romanovsky
2021-09-23 18:12 ` [PATCH net-next 5/6] ice: Delete always true check of PF pointer Leon Romanovsky
2021-09-23 18:12 ` [PATCH net-next 6/6] qed: Don't ignore devlink allocation failures Leon Romanovsky
2021-09-23 22:55 ` [PATCH net-next 0/6] Batch of devlink related fixes Jakub Kicinski
2021-09-23 23:16 ` Leon Romanovsky
2021-09-24 13:14 ` David Miller
2021-09-25 8:56 ` Leon Romanovsky [this message]
2021-09-24 13:20 ` patchwork-bot+netdevbpf
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=YU7kVo2MHe7Bq1Or@unreal \
--to=leon@kernel.org \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=GR-everest-linux-l2@marvell.com \
--cc=aelior@marvell.com \
--cc=alobakin@pm.me \
--cc=anirudh.venkataramanan@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=irusskikh@marvell.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jejb@linux.ibm.com \
--cc=jesse.brandeburg@intel.com \
--cc=jhasan@marvell.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michael.chan@broadcom.com \
--cc=michal.kalderon@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=sathya.perla@broadcom.com \
--cc=skashyap@marvell.com \
--cc=vasundhara-v.volam@broadcom.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;
as well as URLs for NNTP newsgroup(s).