public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Lee Jones <lee@kernel.org>
Cc: Raymond Hackley <raymondhackley@protonmail.com>,
	linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Luca Weiss <luca@z3ntu.xyz>,
	"open list:LED SUBSYSTEM" <linux-leds@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	dev.mbornand@systemb.ch
Subject: Re: [PATCH 1/2] dt-bindings: leds: sgm3140: Document richtek,rt5033 compatible
Date: Wed, 21 Jun 2023 20:17:24 +0100	[thread overview]
Message-ID: <20230621-conceded-groin-e72f91347b30@spud> (raw)
In-Reply-To: <20230621170524.GJ10378@google.com>

[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]

On Wed, Jun 21, 2023 at 06:05:24PM +0100, Lee Jones wrote:
> On Wed, 21 Jun 2023, Conor Dooley wrote:
> > On Wed, Jun 21, 2023 at 04:03:02PM +0100, Lee Jones wrote:
> > > On Wed, 21 Jun 2023, Lee Jones wrote:
> > > > On Fri, 02 Jun 2023, Raymond Hackley wrote:

> > > It's unusual for me to have to dump through a bunch of hoops just to
> > > read and then subsequently reply to mail.  Can you consider removing
> > > whatever encryption you have enabled please?
> > 
> > https://www.kernel.org/doc/html/latest/process/email-clients.html#proton-mail
> 
> Thanks for the link.  This is perfect!

Ye, no worries chief. I got yelled at about it when I started out, so
figured I should at least document it after I noticed others getting
yelled at for the same reason, since it is a bit insidious.

> At least I know it's not just me being unreasonable.
> 
> > I was under the impression that there was no way to disable this
> > behaviour, but I saw mention somewhere that they managed to patch the
> > open source version of the protonmail bridge to function. I cannot find
> > this on lore, because the person's domain was not a proton one and I
> > completely forget their name as it was several months ago.
> > I'll reply here if I find it.

It was Marc Bornand. Add to CC.

Thanks,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-06-21 19:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 13:06 [PATCH 0/2] leds: sgm3140: Add richtek,rt5033-led compatible Raymond Hackley
2023-06-02 13:11 ` [PATCH 1/2] dt-bindings: leds: sgm3140: Document richtek,rt5033 compatible Raymond Hackley
2023-06-21 15:01   ` Lee Jones
2023-06-21 15:03     ` Lee Jones
2023-06-21 15:42       ` Conor Dooley
2023-06-21 17:05         ` Lee Jones
2023-06-21 19:17           ` Conor Dooley [this message]
2023-06-21 17:47     ` Raymond Hackley
2023-06-21 17:56     ` [RESEND PATCH " Raymond Hackley
2023-06-21 18:09   ` [PATCH " Lee Jones
2023-06-02 13:11 ` [PATCH 2/2] leds: sgm3140: Add richtek,rt5033-led compatible Raymond Hackley
2023-06-21 18:09   ` Lee Jones

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=20230621-conceded-groin-e72f91347b30@spud \
    --to=conor@kernel.org \
    --cc=dev.mbornand@systemb.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=luca@z3ntu.xyz \
    --cc=pavel@ucw.cz \
    --cc=raymondhackley@protonmail.com \
    --cc=robh+dt@kernel.org \
    /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