From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 44344EB64D7 for ; Wed, 21 Jun 2023 17:05:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229995AbjFURFd (ORCPT ); Wed, 21 Jun 2023 13:05:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50686 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229501AbjFURFc (ORCPT ); Wed, 21 Jun 2023 13:05:32 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C780610D; Wed, 21 Jun 2023 10:05:31 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 01F5261601; Wed, 21 Jun 2023 17:05:30 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8B3EEC433C8; Wed, 21 Jun 2023 17:05:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1687367129; bh=VgDrDN1AlEKLSxfcxPdZIOC6m3JNO0J57lFupt0/nRM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=tkiqn8dhJ2BLxGzsNwrl7GH0zA9Q2H5HA2XY0mrYmVXJ6UNtMexUiyMjqkDv5Kgik wvjbpIdNK5OTZmbd6YaDrpat/twBHL9TgvP7hTZwo/6AZqFuP/KZt1YU71JyjrBkFO gRG0hut4nnXW1zF5UzAVUXGNU9oUj70HB46C8QPdCwUrBQyw6GAWxKgYaIEQNNehom m5pTHhEnmjfSimTT5xIpvfOZI1kPNyLgocS54PZmAyCBiF8AqzZvy9hUViASUnIRNU RbnC+T8/mx9jvkucXKyxDUIy5CehRIMGzejVLjXtZ58N1UPzY6R6Joz8NEsYzwxbts xq58MM9uoNpcQ== Date: Wed, 21 Jun 2023 18:05:24 +0100 From: Lee Jones To: Conor Dooley Cc: Raymond Hackley , linux-kernel@vger.kernel.org, Pavel Machek , Rob Herring , Krzysztof Kozlowski , Luca Weiss , "open list:LED SUBSYSTEM" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" Subject: Re: [PATCH 1/2] dt-bindings: leds: sgm3140: Document richtek,rt5033 compatible Message-ID: <20230621170524.GJ10378@google.com> References: <20230602130644.259933-1-raymondhackley@protonmail.com> <20230602131009.260239-1-raymondhackley@protonmail.com> <20230621150141.GE10378@google.com> <20230621150302.GF10378@google.com> <20230621-stuffed-revolt-435d3d2dd4aa@spud> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20230621-stuffed-revolt-435d3d2dd4aa@spud> Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Wed, 21 Jun 2023, Conor Dooley wrote: > Raymond, > > 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: > > > > > > > Add devicetree binding for Richtek RT5033 Flash LED charge pump used for > > > > camera flash LEDs. > > > > > > > > Signed-off-by: Raymond Hackley > > > > --- > > > > Documentation/devicetree/bindings/leds/leds-sgm3140.yaml | 1 + > > > > 1 file changed, 1 insertion(+) > > > > > > > > diff --git a/Documentation/devicetree/bindings/leds/leds-sgm3140.yaml b/Documentation/devicetree/bindings/leds/leds-sgm3140.yaml > > > > index 4d2ffe5fcfc7..37d2a93780ab 100644 > > > > --- a/Documentation/devicetree/bindings/leds/leds-sgm3140.yaml > > > > +++ b/Documentation/devicetree/bindings/leds/leds-sgm3140.yaml > > > > @@ -20,6 +20,7 @@ properties: > > > > compatible: > > > > enum: > > > > - ocs,ocp8110 > > > > + - richtek,rt5033-led > > > > > > Why is "-led" appended on to this one and not the others? > > > > 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! 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. Thanks. -- Lee Jones [李琼斯]