From: Breno Leitao <leitao@debian.org>
To: Dave Marquardt <davemarq@linux.ibm.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org
Subject: Re: [PATCH] Fixed typo in netdevsim documentation
Date: Thu, 12 Jun 2025 09:07:03 -0700 [thread overview]
Message-ID: <aEr7J0UbSFhJ0Zn9@gmail.com> (raw)
In-Reply-To: <20250612153742.11310-1-davemarq@linux.ibm.com>
Hello Dave,
On Thu, Jun 12, 2025 at 10:37:42AM -0500, Dave Marquardt wrote:
> Fixed a typographical error in "Rate objects" section
>
> Signed-off-by: Dave Marquardt <davemarq@linux.ibm.com>
Reviewed-by: Breno Leitao <leitao@debian.org>
Thanks for the patch, it is correct, but, there are a few things that
you probably want to fix and resend.
1) You need to choose the tree you want to send. Usually `net-next` or
`net`. In you case, I suppose it can go to documentation tree also.
https://docs.kernel.org/process/maintainer-netdev.html#git-trees-and-patch-flow
and
https://docs.kernel.org/process/maintainer-netdev.html#indicating-target-tree
2) If sent to the netdev, you need to have the maintainers in to/cc. The
tool `b4` helps with that.
prev parent reply other threads:[~2025-06-12 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 15:37 [PATCH] Fixed typo in netdevsim documentation Dave Marquardt
2025-06-12 16:07 ` Breno Leitao [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=aEr7J0UbSFhJ0Zn9@gmail.com \
--to=leitao@debian.org \
--cc=davemarq@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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).