DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org,
	Kevin Laatz <kevin.laatz@intel.com>,
	 Robin Jarry <rjarry@redhat.com>,
	Kevin Traynor <ktraynor@redhat.com>
Subject: Re: [PATCH] dma/idxd: add device ids for new HW versions
Date: Tue, 11 Feb 2025 14:20:51 +0100	[thread overview]
Message-ID: <CAJFAV8zTpB3EzZJeb2mpW0UqAfaMVjBYat7L+pLaYYpYwcEnwA@mail.gmail.com> (raw)
In-Reply-To: <20250130172624.1450975-2-bruce.richardson@intel.com>

On Thu, Jan 30, 2025 at 6:27 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> Add in two extra PCI device id's for future HW versions to be
> supported by idxd driver. This aligns with the definitions present
> in kernel idxd driver [1].
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/dma/idxd/registers.h#n9
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> Cc: stable@dpdk.org
>
> Since this only adds a couple of device IDs, and there are no other
> changes to the dma/idxd driver in 25.03, perhaps this could be
> considered for backport for 24.11?

I prefer not to mark with Cc: stable@dpdk.org, because this is too
vague and LTS maintainers may apply this for 22.11 or 23.11.
For this special request against 24.11, the simpler is to send an
explicit backport request to stable@dpdk.org with a 24.11 prefix in
the title (and copy Kevin, who handles 24.11).

Patch applied, thanks.


-- 
David Marchand


  parent reply	other threads:[~2025-02-11 13:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-30 17:26 Bruce Richardson
2025-01-31 15:05 ` Bruce Richardson
2025-02-06 20:13 ` Patrick Robb
2025-02-11 11:57 ` Kevin Laatz
2025-02-11 13:20 ` David Marchand [this message]
2025-02-11 13:47   ` Bruce Richardson

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=CAJFAV8zTpB3EzZJeb2mpW0UqAfaMVjBYat7L+pLaYYpYwcEnwA@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=kevin.laatz@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=rjarry@redhat.com \
    --cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).