linux-kernel - Re: [PATCH v3] dt-bindings: spi: brcm,bcm2835-spi: convert to dtschema

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAGLn_=vpdnDaMoNNqnON5jBuq4LGtAq+gZm-W-f6H-PXQGMfKA@mail.gmail.com>
Date: Thu, 16 May 2024 15:00:15 +0530
From: Kanak Shilledar <kanakshilledar@...il.com>
To: Conor Dooley <conor.dooley@...rochip.com>
Cc: Conor Dooley <conor@...nel.org>, wahrenst@....net, 
	Kanak Shilledar <kanakshilledar111@...tonmail.com>, Mark Brown <broonie@...nel.org>, 
	Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, 
	Conor Dooley <conor+dt@...nel.org>, Florian Fainelli <florian.fainelli@...adcom.com>, 
	Ray Jui <rjui@...adcom.com>, Scott Branden <sbranden@...adcom.com>, 
	Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>, linux-spi@...r.kernel.org, 
	devicetree@...r.kernel.org, linux-rpi-kernel@...ts.infradead.org, 
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] dt-bindings: spi: brcm,bcm2835-spi: convert to dtschema

On Thu, May 16, 2024 at 12:27 PM Conor Dooley
<conor.dooley@...rochip.com> wrote:
>
> On Thu, May 16, 2024 at 12:00:29PM +0530, Kanak Shilledar wrote:
> > On Tue, May 14, 2024 at 11:44 PM Conor Dooley <conor@...nel.org> wrote:
> > >
> > > On Tue, May 14, 2024 at 12:30:47PM +0530, Kanak Shilledar wrote:
> > >
> > > > Changes in v3:
> > > > - Updated DCO email address
> > >
> > > I was really hoping you'd tell me why you'd not used the same email
> > > address, rather than just sending another version. My ulterior motive is
> > > that I wrote the section in email-clients.rst saying that protonmail had
> > > WKD issues with kernel.org accounts but apparently proton added a
> > > workaround and have yet to be sent an email that confirmed that the
> > > workaround fixed things. (I'm not sure that the WKD issues ever applied
> > > as there's no GPG key posted for conor+dt@...nel.org, only
> > > conor@...nel.org).
> >
> > Oh, I am primarily using protonmail and I am aware that there are some
> > issues with protonmail and kernel.org so for that reason I am sending my
> > patches via @gmail.com address. I was trying out some things with
> > gmail and proton so had changed my signing email address to @gmail.com
> > apart from sending emails I have no motive on using gmail.com account.
> > Also I am adding my protonmail account in the `CC`.
> > Hope this helps.
> > If this is not the intended route then I will change it and stick
> > to one email address.
>
> I don't care what email you use for stuff, that's your business. I just
> want to know if we can remove the section from the docs that says not to
> use proton. Maybe you could send me an off-list email to
> conor@...nel.org from your proton account, so I can see if it ends up
> getting encrypted? That'd be helpful if you could.

I have sent you a mail off-list using proton. Please let me know if
you were able to view it?
There is a option to attach public key as well when using protonmail.

> > > The patch is fine IMO though, so
> > > Reviewed-by: Conor Dooley <conor.dooley@...rochip.com>
> >
> > Do I need to roll out another version with this reviewed by flag?
>
> No, Mark should be able to pick that up. There's usually no need to
> resend patches solely pick up tags, that's the maintainer's
> responsibility. If you're resending for any other reason, then yes, pick
> up tags.

Alright!
> Cheers,
> Conor.

Thanks and Regards,
Kanak Shilledar