netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?UGFsaSBSb2jDoXIgPHBhbGlAa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: paulus@samba.org, davem@davemloft.net, kuba@kernel.org,
	g.nault@alphalink.fr, linux-ppp@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ppp: Fix generating ppp unit id when ifname is not specified
Date: Sun, 08 Aug 2021 12:10:06 +0000	[thread overview]
Message-ID: <162842460623.22263.8898241891049192609.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210807160050.17687-1-pali@kernel.org>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Sat,  7 Aug 2021 18:00:50 +0200 you wrote:
> When registering new ppp interface via PPPIOCNEWUNIT ioctl then kernel has
> to choose interface name as this ioctl API does not support specifying it.
> 
> Kernel in this case register new interface with name "ppp<id>" where <id>
> is the ppp unit id, which can be obtained via PPPIOCGUNIT ioctl. This
> applies also in the case when registering new ppp interface via rtnl
> without supplying IFLA_IFNAME.
> 
> [...]

Here is the summary with links:
  - ppp: Fix generating ppp unit id when ifname is not specified
    https://git.kernel.org/netdev/net/c/3125f26c5148

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



      reply	other threads:[~2021-08-08 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-07 16:00 [PATCH] ppp: Fix generating ppp unit id when ifname is not specified Pali Rohár
2021-08-08 12: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=162842460623.22263.8898241891049192609.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?b?UGFsaSBSb2jDoXIgPHBhbGlAa2VybmVsLm9yZz4=?=@ci.codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=g.nault@alphalink.fr \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ppp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulus@samba.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).