netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Fran=C3=A7ois_Michel_=3Cfrancois=2Emichel=40uclouvain=2Ebe=3E?=@ci.codeaurora.org
Cc: netdev@vger.kernel.org, stephen@networkplumber.org,
	petrm@nvidia.com, dsahern@kernel.org
Subject: Re: [PATCH iproute2-next 0/1] tc: fix typo in netem's usage string
Date: Wed, 30 Aug 2023 19:10:23 +0000	[thread overview]
Message-ID: <169342262317.25071.14337036719848362412.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230830150531.44641-1-francois.michel@uclouvain.be>

Hello:

This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:

On Wed, 30 Aug 2023 17:05:20 +0200 you wrote:
> From: François Michel <francois.michel@uclouvain.be>
> 
> Fixes a misplaced newline in netem's usage string.
> 
> François Michel (1):
>   tc: fix typo in netem's usage string
> 
> [...]

Here is the summary with links:
  - [iproute2-next,1/1] tc: fix typo in netem's usage string
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=865dd3ab1580

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-08-30 19:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 15:05 [PATCH iproute2-next 0/1] tc: fix typo in netem's usage string francois.michel
2023-08-30 15:05 ` [PATCH iproute2-next 1/1] " francois.michel
2023-08-30 15:32   ` Petr Machata
2023-08-30 19:00     ` David Ahern
2023-08-31  9:05     ` Donald Hunter
2023-08-31  9:12       ` François Michel
2023-08-30 19:00 ` [PATCH iproute2-next 0/1] " David Ahern
2023-08-30 19:10 ` patchwork-bot+netdevbpf [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=169342262317.25071.14337036719848362412.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?q?Fran=C3=A7ois_Michel_=3Cfrancois=2Emichel=40uclouvain=2Ebe=3E?=@ci.codeaurora.org \
    --cc=dsahern@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=petrm@nvidia.com \
    --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 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).