From: Kanak Shilledar <kanakshilledar@gmail.com>
To: Conor Dooley <conor@kernel.org>
Cc: 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
Subject: Re: [PATCH v3] dt-bindings: spi: brcm,bcm2835-spi: convert to dtschema
Date: Thu, 16 May 2024 12:00:29 +0530 [thread overview]
Message-ID: <CAGLn_=vRDj_A2VpqQ6eT3OX6AgCfesA1KzJh+6djyF6MhAgEvw@mail.gmail.com> (raw)
In-Reply-To: <20240514-sitting-ritzy-498d35eb5ac8@spud>
On Tue, May 14, 2024 at 11:44 PM 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 applied
> 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 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.
> 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?
> Cheers,
> Conor.
Thanks and Regards
Kanak Shilledar
next prev parent reply other threads:[~2024-05-16 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 7:00 [PATCH v3] dt-bindings: spi: brcm,bcm2835-spi: convert to dtschema Kanak Shilledar
2024-05-14 18:14 ` Conor Dooley
2024-05-16 6:30 ` Kanak Shilledar [this message]
2024-05-16 6:56 ` Conor Dooley
2024-05-16 9:30 ` Kanak Shilledar
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='CAGLn_=vRDj_A2VpqQ6eT3OX6AgCfesA1KzJh+6djyF6MhAgEvw@mail.gmail.com' \
--to=kanakshilledar@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=kanakshilledar111@protonmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=wahrenst@gmx.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).