From: John 'Warthog9' Hawley <warthog9@kernel.org>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>, "Jakub Kicinski" <kuba@kernel.org>
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
Subject: Re: [PATCH net] net: dsa: mt7530: fix tristate and help description
Date: Thu, 26 Jan 2023 00:12:07 -0800 [thread overview]
Message-ID: <9539b880-642d-9ac5-ccfa-2b237548f4fc@kernel.org> (raw)
In-Reply-To: <c4b65e0d-ce10-1fa4-d468-ba50a5441778@arinc9.com>
On 1/25/2023 11:48 PM, Arınç ÜNAL wrote:
> On 26.01.2023 10:45, John 'Warthog9' Hawley wrote:
>> On 1/25/2023 11:34 PM, Arınç ÜNAL wrote:
>>> On 26.01.2023 10:23, John 'Warthog9' Hawley wrote:
>>>> On 1/25/2023 10:44 PM, Jakub Kicinski wrote:
>>>>> 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.
>>>>>
>>>>
>>>> You are also likely to run into trouble if your character set is set
>>>> to UTF-8.
>>>
>>> I think that may be the problem here. I just resent this with only
>>> Jakub and the lists without names. It didn't make it to netdev. My
>>> name includes non-Latin characters. I'm not sure how I can change
>>> UTF-8 to something else that works with this list. I had no such
>>> issues with linux-mediatek.
>>>
>>> Arınç
>>>
>>
>> So dug it out of the logs, you aren't running into UTF-8 issues, so
>> that's good. However your mail client is appending 'Delivered-To:' to
>> the messages, which is a significant indicator of some weird mail
>> problem for lists, I.E. why is a message that's been delivered being
>> passed back through to the list, which is on the published taboo list:
>>
>> http://vger.kernel.org/majordomo-taboos.txt
>>
>> What are you using to send these messages, as that's a header I
>> absolutely wouldn't expect to be on messages heading to vger?
>
> It's just git send-email on git version 2.37.2. Zoho is doing the
> hosting & SMTP.
>
> Arınç
>
Best I can suggest for testing is try sending the patch series to only
the following 2 e-mail addresses:
to: testing@vger.kernel.org
cc: warthog9@eaglescrag.net
That will cut out more or less everything in the interim and might get
me a better look at the series.
Only other thing I can think of is how is git send-email configured?
Where the 'Delivered-To:' header is in the headers makes me think that
it's added somewhere in what zoho is doing, which doesn't particularly
make any sense, as that would imply you are sending it to yourself and
then it passes it on?
I'll admit zoho is one of the mail providers that has a tendency to
reject a lot of mail coming from vger and has been unresponsive to any
queries I've made on that front (though I'll note your domain is not on
the list of domains that are having problems there). Only other thing I
could suggest is pinging zoho technical support and asking them what's
up, as that's a very odd header to have there.
- John 'Warthog9' Hawley
next prev parent reply other threads:[~2023-01-26 8:12 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
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 [this message]
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=9539b880-642d-9ac5-ccfa-2b237548f4fc@kernel.org \
--to=warthog9@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®