Re: [PATCH net] net: dsa: mt7530: fix tristate and help description

[Arınç ÜNAL]

Removing lists from recipient.

On 26.01.2023 12:13, Arınç ÜNAL wrote:
> On 26.01.2023 12:00, Arınç ÜNAL wrote:
> > On 26.01.2023 11:51, John 'Warthog9' Hawley wrote:
> > > Popping the lists off -JH
> > >
> > > On 1/26/2023 12:24 AM, Arınç ÜNAL wrote:
> > > > On 26.01.2023 11:12, John 'Warthog9' Hawley wrote:
> > > > > 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@xxxxxxxxxx>
> > > > > > > > > >
> > > > > > > > > > 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@xxxxxxxxxxxxxxx
> > > > >      cc: warthog9@xxxxxxxxxxxxxx
> > > > >
> > > > > That will cut out more or less everything in the interim and might 
> > > > > get me a better look at the series.
> > > >
> > > > Done, thanks for looking over this.
> > >
> > > Got the the patch, and the test list does flag it for taboo, so at 
> > > least it's consistent.
> > >
> > > Looking at the headers to my direct e-mail it's still got the 
> > > delivered-to header so zoho is doing something they shouldn't be doing:
> > >
> > > Received: from sender4-op-o14.zoho.com (sender4-op-o14.zoho.com 
> > > [136.143.188.14])
> > >      by mail.monkeyblade.net (Postfix) with ESMTPS id 7F14F83ED027
> > >      for <warthog9@xxxxxxxxxxxxxx>; Thu, 26 Jan 2023 00:17:53 -0800 
> > > (PST)
> > > X-Virus-Status: Clean
> > > X-Virus-Scanned: clamav-milter 0.103.7 at shards.monkeyblade.net
> > > Delivered-To: arinc.unal@xxxxxxxxxx
> > > ARC-Seal: i=1; a=rsa-sha256; t=1674721072; cv=none;
> > >      d=zohomail.com; s=zohoarc;
> > >
> > > > > 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?
> > > >
> > > > My .gitconfig is as follows, the rest is straight out of apt install 
> > > > git-email.
> > > >
> > > > [user]
> > > >          email = arinc.unal@xxxxxxxxxx
> > > >          name = Arınç ÜNAL
> > > >
> > > > [sendemail]
> > > >          smtpEncryption = ssl
> > > >          smtpServer = smtppro.zoho.com
> > > >          smtpUser = arinc.unal@xxxxxxxxxx
> > > >          smtpPass =
> > > >          smtpServerPort = 465
> > >
> > > That looks utterly boring and exactly how I would hope to find it, so 
> > > that's probably not it.
> > >
> > > Between that config, and the headers I'm seeing from zoho to shards, 
> > > noted above, I'm pretty sure they are adding it and they absolutely 
> > > shouldn't be...
> > >
> > > > > 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.
> > > >
> > > > I'll see what I can do. I've been getting suspicious header mails 
> > > > from linux-arm-kernel and pabeni@xxxxxxxxxx's mail server outright 
> > > > claims Zoho's SMTP IP as spam.
> > > >
> > > > Your mail to 'linux-arm-kernel' with the subject
> > > >
> > > >      [PATCH net] net: ethernet: mtk_eth_soc: disable hardware DSA
> > > > untagging for second MAC
> > > >
> > > > Is being held until the list moderator can review it for approval.
> > > >
> > > > The reason it is being held:
> > > >
> > > >      Message has a suspicious header
> > >
> > > 1 $local_currency_unit says it's a 'Delivered-To:' header ;-)
> > >
> > > > ---
> > > >
> > > > This message was created automatically by mail delivery software.
> > > >   A message that you sent could not be delivered to one or more of 
> > > > its recipients. This is a permanent error.
> > > >
> > > > pabeni@xxxxxxxxxx, ERROR CODE :550 - spamcop.mimecast.org Blocked - 
> > > > see https://www.spamcop.net/bl.shtml?136.143.188.14. - 
> > > > https://community.mimecast.com/docs/DOC-1369#550 
> > > > [nSq2mM6RNqWOxCrbHVMv8Q.us380]
> > >
> > > Hmmmm wonder what they ran afoul of to trigger spamcop.  The IP isn't 
> > > listed on mxtoolbox ( 
> > > https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a136.143.188.14&run=toolpage )
> > >
> > > and weirdly it's also not listed on spamcop.net itself:
> > >
> > > https://www.spamcop.net/w3m?action=blcheck&ip=136.143.188.14
> > >
> > > Could be a generic response message via mimecast but it might be 
> > > kicking it back similarly on the odd headers.  Either way something 
> > > is definitely wonky with the way zoho's handling e-mail and
> > >
> > > On a side note for Paolo, any way you can check with Redhat IT and 
> > > see if they can fish out a reason for the rejection from their mail 
> > > logs? Might prove helpful to Arınç, though I'm not entirely hopeful 
> > > for Zoho's support being able to remedy this.
> > >
> > > Your best bet is to check with Zoho directly, my own experience tends 
> > > to be since I'm not the paying customer I tend to be ignored or 'we 
> > > can't talk to you'.  If you need any logs or the headers let me know 
> > > and I'll snag them for you.
> >
> > Let's see if this mail reaches the list. I suspect Delivered-To: 
> > header is being added by Zoho when git send-email automatically adds 
> > my own address to CC. My normal responses end up on the list fine.
>
> I forgot to add the lists back, oops. Take two.

Yeah it didn't reach the list. I'll tell Zoho to stop adding this header 
when my own address is on CC. Thanks for the help John!

Arınç