All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Qingfang Deng <dqfext@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, mitch@sfgoth.com,
	horms@kernel.org, linux-ppp@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] ppp: simplify input error handling
Date: Tue, 10 Mar 2026 02:20:14 +0000	[thread overview]
Message-ID: <177310921454.2028885.14368988773145653916.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260306093649.1048232-1-dqfext@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri,  6 Mar 2026 17:36:49 +0800 you wrote:
> Currently, ppp_input_error() indicates an error by allocating a 0-length
> skb and calling ppp_do_recv(). It takes an error code argument, which is
> stored in skb->cb, but not used by ppp_receive_frame().
> 
> Simplify the error handling by removing the unused parameter and the
> unnecessary skb allocation. Instead, call ppp_receive_error() directly
> from ppp_input_error() under the recv lock, and the length check in
> ppp_receive_frame() can be removed.
> 
> [...]

Here is the summary with links:
  - [net-next] ppp: simplify input error handling
    https://git.kernel.org/netdev/net-next/c/abb0eb0b033a

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



      reply	other threads:[~2026-03-10  2:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06  9:36 [PATCH net-next] ppp: simplify input error handling Qingfang Deng
2026-03-10  2:20 ` 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=177310921454.2028885.14368988773145653916.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dqfext@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ppp@vger.kernel.org \
    --cc=mitch@sfgoth.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.