diff mbox series

[meta-dpdk] README: change mailing list for patch contribution

Message ID 20251216021516.2600042-1-anuj.mittal@oss.qualcomm.com
State New
Headers show
Series [meta-dpdk] README: change mailing list for patch contribution | expand

Commit Message

Anuj Mittal Dec. 16, 2025, 2:15 a.m. UTC 
From: Anuj Mittal <anuj.mittal@oss.qualcomm.com>

yocto-patches is a more appropriate list for meta-dpdk since this is not
Intel specific.

Also, include my new email address.

Signed-off-by: Anuj Mittal <anuj.mittal@oss.qualcomm.com>
---
 README | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Comments

Quentin Schulz Dec. 16, 2025, 9:38 a.m. UTC | #1 
Hi Anuj,

On 12/16/25 3:15 AM, Anuj Mittal via lists.yoctoproject.org wrote:
> [You don't often get email from anuj.mittal=oss.qualcomm.com@lists.yoctoproject.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> From: Anuj Mittal <anuj.mittal@oss.qualcomm.com>
> 
> yocto-patches is a more appropriate list for meta-dpdk since this is not
> Intel specific.
> 

I don't see any mention of adding [meta-dpdk] subject (and how to do it) 
so that a patch sent to the ML is known to be applied to that tree? See 
https://git.yoctoproject.org/meta-rockchip/tree/README#n251 for an example.

You may want to add a .b4-config, see 
https://git.yoctoproject.org/meta-rockchip/tree/.b4-config for an 
example. See https://b4.docs.kernel.org/ for documentation on that tool :)

Cheers,
Quentin
diff mbox series

Patch

diff --git a/README b/README
index 81703cf..2901214 100644
--- a/README
+++ b/README
@@ -20,8 +20,8 @@  This layer depends on:
 Guidelines for submitting patches
 ====================================
 
-Please submit any patches against meta-dpdk to the meta-intel
-mailing list (meta-intel@lists.yoctoproject.org). Also, if your patches are
+Please submit any patches against meta-dpdk to the yocto-patches
+mailing list (yocto-patches@lists.yoctoproject.org). Also, if your patches are
 available via a public git repository, please also include a URL to
 the repo and branch containing your patches as that makes it easier
 for maintainers to grab and test your patches.
@@ -69,4 +69,4 @@  a patch or patchset within 24 hours of the time it was posted.  For
 larger and/or more involved patches and patchsets, the review process
 may take longer.
 
-Maintainer: Anuj Mittal <anuj.mittal@intel.com>
+Maintainer: Anuj Mittal <anuj.mittal@oss.qualcomm.com>