From: patchwork-bot+netdevbpf@kernel.org
To: None <arinc9.unal@gmail.com>
Cc: andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, arinc.unal@arinc9.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, erkin.bozoglu@xeront.com
Subject: Re: [PATCH net] net: dsa: mt7530: fix tristate and help description
Date: Sat, 28 Jan 2023 06:40:19 +0000 [thread overview]
Message-ID: <167488801907.1883.686729711834531157.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230126190110.9124-1-arinc.unal@arinc9.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 26 Jan 2023 22:01:11 +0300 you wrote:
> From: Arınç ÜNAL <arinc.unal@arinc9.com>
>
> Fix description for tristate and help sections which include inaccurate
> information.
>
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
>
> [...]
Here is the summary with links:
- [net] net: dsa: mt7530: fix tristate and help description
https://git.kernel.org/netdev/net/c/ff445b839774
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-01-28 6:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 19:01 [PATCH net] net: dsa: mt7530: fix tristate and help description arinc9.unal
2023-01-28 6:40 ` patchwork-bot+netdevbpf [this message]
[not found] <20230125053653.6316-1-arinc.unal@arinc9.com>
2023-01-26 6:44 ` Jakub Kicinski
2023-01-26 7:23 ` John 'Warthog9' Hawley
2023-01-26 7:34 ` Arınç ÜNAL
2023-01-26 7:45 ` John 'Warthog9' Hawley
2023-01-26 7:48 ` Arınç ÜNAL
2023-01-26 8:12 ` John 'Warthog9' Hawley
2023-01-26 8:24 ` Arınç ÜNAL
[not found] ` <191747ad-fe90-7510-055c-1a31771818e5@eaglescrag.net>
[not found] ` <78e7c3c3-4d8b-3812-28f6-cd04297d465c@arinc9.com>
[not found] ` <173da36f-e912-4f41-a15d-ee1542766ac3@arinc9.com>
2023-01-26 9:39 ` Arınç ÜNAL
2023-01-31 17:04 ` Arınç ÜNAL
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=167488801907.1883.686729711834531157.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=arinc.unal@arinc9.com \
--cc=arinc9.unal@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=erkin.bozoglu@xeront.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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.