Received-SPF: pass (google.com: domain of linux-kernel+bounces-180839-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Precedence: bulk
MIME-Version: 1.0
References: <20240514070051.2959-1-kanakshilledar111@protonmail.com>
 <20240514-sitting-ritzy-498d35eb5ac8@spud> <CAGLn_=vRDj_A2VpqQ6eT3OX6AgCfesA1KzJh+6djyF6MhAgEvw@mail.gmail.com>
 <20240516-encourage-bouncing-77e9c14c9887@wendy>
In-Reply-To: <20240516-encourage-bouncing-77e9c14c9887@wendy>
From: Kanak Shilledar <kanakshilledar@gmail.com>
Date: Thu, 16 May 2024 15:00:15 +0530
Message-ID: <CAGLn_=vpdnDaMoNNqnON5jBuq4LGtAq+gZm-W-f6H-PXQGMfKA@mail.gmail.com>
Subject: Re: [PATCH v3] dt-bindings: spi: brcm,bcm2835-spi: convert to dtschema
To: Conor Dooley <conor.dooley@microchip.com>
Cc: Conor Dooley <conor@kernel.org>, wahrenst@gmx.net, 
	Kanak Shilledar <kanakshilledar111@protonmail.com>, Mark Brown <broonie@kernel.org>, 
	Rob Herring <robh@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, 
	Conor Dooley <conor+dt@kernel.org>, Florian Fainelli <florian.fainelli@broadcom.com>, 
	Ray Jui <rjui@broadcom.com>, Scott Branden <sbranden@broadcom.com>, 
	Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>, linux-spi@vger.kernel.org, 
	devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org, 
	linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, May 16, 2024 at 12:27=E2=80=AFPM Conor Dooley
<conor.dooley@microchip.com> wrote:
>
> On Thu, May 16, 2024 at 12:00:29PM +0530, Kanak Shilledar wrote:
> > On Tue, May 14, 2024 at 11:44=E2=80=AFPM Conor Dooley <conor@kernel.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 appli=
ed
> > > as there's no GPG key posted for conor+dt@kernel.org, only
> > > conor@kernel.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 m=
y
> > 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@kernel.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@microchip.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