From: Jakub Kicinski <kuba@kernel.org>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
erkin.bozoglu@xeront.com,
John 'Warthog9' Hawley <warthog9@kernel.org>
Subject: Re: [PATCH net] net: dsa: mt7530: fix tristate and help description
Date: Wed, 25 Jan 2023 22:44:11 -0800 [thread overview]
Message-ID: <20230125224411.5a535817@kernel.org> (raw)
In-Reply-To: <20230125053653.6316-1-arinc.unal@arinc9.com>
On Wed, 25 Jan 2023 08:36:53 +0300 Arınç ÜNAL wrote:
> Fix description for tristate and help sections which include inaccurate
> information.
>
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
Didn't make it thru to the list again :(
Double check that none of the addresses in To: or Cc: are missing
spaces between name and email or after a dot. That seems to be the most
common cause of trouble. Or try to resend using just emails, no names.
next parent reply other threads:[~2023-01-26 6:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230125053653.6316-1-arinc.unal@arinc9.com>
2023-01-26 6:44 ` Jakub Kicinski [this message]
2023-01-26 7:23 ` [PATCH net] net: dsa: mt7530: fix tristate and help description 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
2023-01-26 19:01 arinc9.unal
2023-01-28 6:40 ` patchwork-bot+netdevbpf
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=20230125224411.5a535817@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=arinc.unal@arinc9.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=erkin.bozoglu@xeront.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=warthog9@kernel.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 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.