From: patchwork-bot+netdevbpf@kernel.org
To: Markus Elfring <Markus.Elfring@web.de>
Cc: linux-ppp@vger.kernel.org, netdev@vger.kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, jirislaby@kernel.org, pabeni@redhat.com,
qingfang.deng@linux.dev, tparkin@katalix.com,
linux-kernel@vger.kernel.org, kees@kernel.org
Subject: Re: [PATCH v2 net-next] ppp_synctty: Use common error handling code in ppp_sync_txmunge()
Date: Thu, 17 Sep 2026 08:30:04 +0000 [thread overview]
Message-ID: <178963380438.3497657.12392153187415676873.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <15f151c7-58c8-4116-8a03-e985fd132b0f@web.de>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 15 Sep 2026 11:23:01 +0200 you wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Tue, 15 Sep 2026 10:48:11 +0200
>
> Use an additional label so that a bit of exception handling can be better
> reused at the end of this function implementation.
>
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
>
> [...]
Here is the summary with links:
- [v2,net-next] ppp_synctty: Use common error handling code in ppp_sync_txmunge()
https://git.kernel.org/netdev/net-next/c/063510768490
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-17 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 9:23 [PATCH v2 net-next] ppp_synctty: Use common error handling code in ppp_sync_txmunge() Markus Elfring
2026-09-16 12:49 ` Simon Horman
2026-09-17 8:30 ` 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=178963380438.3497657.12392153187415676873.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jirislaby@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qingfang.deng@linux.dev \
--cc=tparkin@katalix.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.