From: "Michal Koutný" <mkoutny@suse.com>
To: netdev@vger.kernel.org
Cc: mkoutny@suse.com, mkubecek@suse.cz,
Davide Benini <davide.benini@suse.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v2 2/2] README.devel: clarify patch rules
Date: Fri, 21 Feb 2025 10:29:27 +0100 [thread overview]
Message-ID: <20250221092927.701552-3-mkoutny@suse.com> (raw)
In-Reply-To: <20250221092927.701552-1-mkoutny@suse.com>
Signed-off-by: Michal Koutný <mkoutny@suse.com>
---
README.devel | 2 ++
1 file changed, 2 insertions(+)
diff --git a/README.devel b/README.devel
index 60c95468..1c80a336 100644
--- a/README.devel
+++ b/README.devel
@@ -16,3 +16,5 @@ aligned on the mainline Linux kernel (ie follows Linus).
The iproute2-next repository tracks the code intended for the next
release; it corresponds with networking development tree (net-next)
in the kernel.
+Patch submitting rules are akin to kernel
+ https://www.kernel.org/doc/html/latest/process/submitting-patches.html
--
2.48.1
prev parent reply other threads:[~2025-02-21 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 9:29 [PATCH v2 0/2] ss: Tone down cgroup path resolution Michal Koutný
2025-02-21 9:29 ` [PATCH v2 1/2] " Michal Koutný
2025-02-21 9:29 ` Michal Koutný [this message]
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=20250221092927.701552-3-mkoutny@suse.com \
--to=mkoutny@suse.com \
--cc=davide.benini@suse.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 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.