All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linuxarm@huawei.com, mauro.chehab@huawei.com,
	John Stultz <john.stultz@linaro.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Some small cleanup/fixes for SPMI driver
Date: Wed, 14 Oct 2020 14:26:36 -0700	[thread overview]
Message-ID: <160271079652.884498.2384315265584338952@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20201003105653.GA117381@kroah.com>

Quoting Greg Kroah-Hartman (2020-10-03 03:56:53)
> On Fri, Oct 02, 2020 at 02:22:17PM -0700, Stephen Boyd wrote:
> > Quoting Mauro Carvalho Chehab (2020-09-28 23:22:11)
> > > Hi Stephen,
> > > 
> > > While double-checking against yesterday's linux-next, I noticed
> > > that those two patches weren't merge yet. 
> > > 
> > > As you replied to both with your Reviewed-by:, are you expecting
> > > them to be merged via someone's tree, or are you intending
> > > to merge them via your tree?
> > 
> > Per the maintainers file I am a reviewer not a maintainer of SPMI.
> > Usually Greg applies patches here. I can collect patches and send them
> > on up if that helps.
> 
> Who is the maintainer?  Having a "reviewer only" is confusing to
> everyone involved, as you might have someone who can review patches, but
> no one to actually merge them anywhere?
> 
> Not a good situation :(
> 

Ok. I can spin up an SPMI tree on kernel.org and make this change to the
MAINTAINERS file (plus whatever tree path I can make). Do you want me to
send you patches in email form as a pull request? I imagine the patch
load will be fairly low.

----8<-----
diff --git a/MAINTAINERS b/MAINTAINERS
index deaafb617361..3e09630455d4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16338,7 +16338,7 @@ F:	Documentation/networking/device_drivers/ethernet/toshiba/spider_net.rst
 F:	drivers/net/ethernet/toshiba/spider_net*
 
 SPMI SUBSYSTEM
-R:	Stephen Boyd <sboyd@kernel.org>
+M:	Stephen Boyd <sboyd@kernel.org>
 L:	linux-arm-msm@vger.kernel.org
 F:	Documentation/devicetree/bindings/spmi/
 F:	drivers/spmi/

  reply	other threads:[~2020-10-14 21:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  6:22 [PATCH v2 0/2] Some small cleanup/fixes for SPMI driver Mauro Carvalho Chehab
2020-09-29  6:22 ` [PATCH v2 1/2] spmi: get rid of a warning when built with W=1 Mauro Carvalho Chehab
2020-11-13 20:47   ` Stephen Boyd
2020-09-29  6:22 ` [PATCH v2 2/2] spmi: fix some coding style issues at the spmi core Mauro Carvalho Chehab
2020-09-29  9:13   ` Marc Gonzalez
2020-11-13 20:47   ` Stephen Boyd
2020-10-02 21:22 ` [PATCH v2 0/2] Some small cleanup/fixes for SPMI driver Stephen Boyd
2020-10-03 10:56   ` Greg Kroah-Hartman
2020-10-14 21:26     ` Stephen Boyd [this message]
2020-10-15 12:55       ` Greg Kroah-Hartman
2020-12-29 20:15 ` patchwork-bot+linux-arm-msm

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=160271079652.884498.2384315265584338952@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mani@kernel.org \
    --cc=mauro.chehab@huawei.com \
    --cc=mchehab+huawei@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.