From: Jason Gunthorpe <jgg@nvidia.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
david.m.ertman@intel.com, shiraz.saleem@intel.com,
mustafa.ismail@intel.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next 0/1] [pull request] iwl-next Intel Wired LAN Driver Updates 2022-02-07
Date: Tue, 8 Feb 2022 13:00:00 -0400 [thread overview]
Message-ID: <20220208170000.GA180855@nvidia.com> (raw)
In-Reply-To: <20220207235921.1303522-1-anthony.l.nguyen@intel.com>
On Mon, Feb 07, 2022 at 03:59:20PM -0800, Tony Nguyen wrote:
> This pull request is targeting net-next and rdma-next branches. RDMA
> patches will be sent to RDMA tree following acceptance of this shared
> pull request. These patches have been reviewed by netdev and RDMA
> mailing lists[1].
>
> Dave adds support for ice driver to provide DSCP QoS mappings to irdma
> driver.
>
> [1] https://lore.kernel.org/netdev/20220202191921.1638-1-shiraz.saleem@intel.com/
> The following are changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
> Linux 5.17-rc1
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/linux iwl-next
No signed tag?
In future can you send these in the standard form so patchworks will
pick them up?
Also please add cover letters so there is something to put in the
merge
But PR applied along with the matching two RDMA patches.
Thanks,
Jason
next prev parent reply other threads:[~2022-02-08 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 23:59 [PATCH net-next 0/1] [pull request] iwl-next Intel Wired LAN Driver Updates 2022-02-07 Tony Nguyen
2022-02-07 23:59 ` [PATCH net-next 1/1] ice: add support for DSCP QoS for IDC Tony Nguyen
2022-02-08 17:00 ` Jason Gunthorpe [this message]
2022-02-08 21:18 ` [PATCH net-next 0/1] [pull request] iwl-next Intel Wired LAN Driver Updates 2022-02-07 Nguyen, Anthony L
2022-02-09 9:50 ` Leon Romanovsky
2022-02-09 17:22 ` Nguyen, Anthony L
2022-02-09 4:45 ` Jakub Kicinski
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=20220208170000.GA180855@nvidia.com \
--to=jgg@nvidia.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mustafa.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shiraz.saleem@intel.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).