From: Thomas Monjalon <thomas@monjalon.net>
To: Srikanth Yalavarthi <syalavarthi@marvell.com>
Cc: "Bruce Richardson" <bruce.richardson@intel.com>,
"David Marchand" <david.marchand@redhat.com>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
dev@dpdk.org, syalavarthi@marvell.com, sshankarnara@marvell.com,
jerinj@marvell.com
Subject: Re: [PATCH v2 1/1] devtools: update sources in build tags script
Date: Wed, 08 Nov 2023 12:24:20 +0100 [thread overview]
Message-ID: <2694831.uZKlY2gecq@thomas> (raw)
In-Reply-To: <20231108092828.17628-1-syalavarthi@marvell.com>
08/11/2023 10:28, Srikanth Yalavarthi:
> As part of deprecating kmods meson option, 'kernel/linux'
> directory is removed from the repository.
>
> This patch removes non-existing 'kernel/linux' directory
> from linux_sources of build tags script.
>
> Fixes: a52d472c5c94 ("build: deprecate kmods meson option")
If it is an old commit, you should probably add Cc: stable@dpdk.org
You can check with devtools/check-git-log.sh
> Signed-off-by: Srikanth Yalavarthi <syalavarthi@marvell.com>
You forgot the ack from Ferruh.
Srikanth, you are sending a lot of patches, which is good :)
but we will ask you to make an effort on getting all details.
You may read again the contributor's guide again.
next prev parent reply other threads:[~2023-11-08 11:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 4:44 [PATCH v1 1/1] devtools: update sources in build tags script Srikanth Yalavarthi
2023-11-08 8:48 ` Ferruh Yigit
2023-11-08 9:29 ` [EXT] " Srikanth Yalavarthi
2023-11-08 9:28 ` [PATCH v2 " Srikanth Yalavarthi
2023-11-08 9:31 ` Morten Brørup
2023-11-08 11:24 ` Thomas Monjalon [this message]
2023-11-08 14:42 ` [EXT] " Srikanth Yalavarthi
2023-11-08 15:23 ` Thomas Monjalon
2023-11-28 10:57 ` Thomas Monjalon
2023-11-08 11:44 ` Ferruh Yigit
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=2694831.uZKlY2gecq@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mb@smartsharesystems.com \
--cc=sshankarnara@marvell.com \
--cc=stephen@networkplumber.org \
--cc=syalavarthi@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.