devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: Mark Hasemeyer <markhas@chromium.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Raul Rangel <rrangel@chromium.org>,
	Bhanu Prakash Maiya <bhanumaiya@chromium.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Benson Leung <bleung@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	chrome-platform@lists.linux.dev, devicetree@vger.kernel.org
Subject: Re: [PATCH v10 2/3] dt-bindings: mfd: Add compatible string for UART support
Date: Thu, 5 Jan 2023 16:27:32 +0000	[thread overview]
Message-ID: <Y7b6dC6dDNO2bVjr@google.com> (raw)
In-Reply-To: <Y7buUdgLfnQqnG+x@google.com>

On Thu, 05 Jan 2023, Tzung-Bi Shih wrote:

> On Thu, Jan 05, 2023 at 02:24:26PM +0000, Lee Jones wrote:
> > On Thu, 05 Jan 2023, Tzung-Bi Shih wrote:
> > 
> > > On Wed, Jan 04, 2023 at 04:08:24PM +0000, Lee Jones wrote:
> > > > On Wed, 07 Dec 2022, Mark Hasemeyer wrote:
> > > > 
> > > > > From: Bhanu Prakash Maiya <bhanumaiya@chromium.org>
> > > > > 
> > > > > Add a compatible string to support the UART implementation of the cros
> > > > > ec interface. The driver does not support the reg and interrupt
> > > > > properties, so exempt them from being required for UART compatible nodes.
> > > > > 
> > > > > Signed-off-by: Bhanu Prakash Maiya <bhanumaiya@chromium.org>
> > > > > Co-developed-by: Mark Hasemeyer <markhas@chromium.org>
> > > > > Signed-off-by: Mark Hasemeyer <markhas@chromium.org>
> > > > > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > > > > ---
> > > > > 
> > > > > Changes in v10:
> > > > > - No change
> > > > > 
> > > [...]
> > > > 
> > > > I changed the subject line and applied the patch, thanks.
> > > 
> > > Pardon me.  I didn't know you would pick the patch so that I have queued it
> > > into chrome-platform[1].  Would you like me to drop the commit?
> > 
> > Yes, please do.
> 
> Dropped in chrome-platform.
> 
> > You should gain permission from the maintainer before you apply patches.
> > 
> >   % scripts/get_maintainer.pl -f Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> >      Lee Jones <lee@kernel.org> (supporter:MULTIFUNCTION DEVICES (MFD))
> >      Rob Herring <robh+dt@kernel.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
> >      Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
> >      Matthias Brugger <matthias.bgg@gmail.com> (maintainer:ARM/Mediatek SoC support)
> 
> I see.  I guess for the case, I should get both MFD and DT bindings
> maintainers' Acks before applying the patch.

Yes.  The situation isn't overly clear and differs from subsystem to
subsystem and maintainer to maintainer.  In the MFD case, Rob and
Krzysztof conduct the first reviews.  99 times out of 100, if they're
happy, I'm happy and I merge the changes via the MFD tree.  Same goes
for Backlight and more recently, LEDs.

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2023-01-05 16:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221207104005.v10.1.If7926fcbad397bc6990dd725690229bed403948c@changeid>
2022-12-07 17:40 ` [PATCH v10 2/3] dt-bindings: mfd: Add compatible string for UART support Mark Hasemeyer
2022-12-07 17:57   ` Krzysztof Kozlowski
2023-01-04 16:08   ` Lee Jones
2023-01-05  1:10     ` Tzung-Bi Shih
2023-01-05 14:13       ` Lee Jones
2023-01-05 14:24       ` Lee Jones
2023-01-05 15:35         ` Tzung-Bi Shih
2023-01-05 16:27           ` Lee Jones [this message]
2023-01-05 18:08             ` Tzung-Bi Shih
2023-01-09 19:06               ` Mark Hasemeyer
2023-01-10 10:24                 ` 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=Y7b6dC6dDNO2bVjr@google.com \
    --to=lee@kernel.org \
    --cc=bhanumaiya@chromium.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=devicetree@vger.kernel.org \
    --cc=groeck@chromium.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markhas@chromium.org \
    --cc=robh+dt@kernel.org \
    --cc=rrangel@chromium.org \
    --cc=tzungbi@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;
as well as URLs for NNTP newsgroup(s).