From: Lee Jones <lee.jones@linaro.org>
To: Johan Hovold <johan@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
Support Opensource <support.opensource@diasemi.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Milo Kim <milo.kim@ti.com>,
patches@opensource.wolfsonmicro.com,
Fabio Estevam <fabio.estevam@freescale.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] mfd: da9052: fix broken regulator probe
Date: Mon, 18 May 2015 11:13:55 +0100 [thread overview]
Message-ID: <20150518101355.GQ22418@x1> (raw)
In-Reply-To: <20150518095159.GB28127@localhost>
On Mon, 18 May 2015, Johan Hovold wrote:
> On Mon, May 18, 2015 at 10:10:49AM +0100, Lee Jones wrote:
> > On Fri, 15 May 2015, Johan Hovold wrote:
> > > On Thu, May 14, 2015 at 08:19:43AM +0100, Lee Jones wrote:
> > > > On Wed, 13 May 2015, Mark Brown wrote:
> > > >
> > > > > On Wed, May 13, 2015 at 05:54:19PM +0100, Lee Jones wrote:
> > > > > > On Wed, 13 May 2015, Mark Brown wrote:
> > > > >
> > > > > > > If you're looking for me to review something you need to send it to me,
> > > > > > > and the chances of me looking at it are very much increased if there's a
> > > > > > > relevant subject line. I'm CCed (not even on the to list) on endless
> > > > > > > large threads and reposts of patch serieses about MFD drivers most of
> > > > > > > which are of very little relevance to me so they get ignored very
> > > > > > > easily.
> > > > >
> > > > > > Calm down dear, it's only a commercial.
> > > > >
> > > > > > I wasn't having a pop. Rather empathising with your situation and
> > > > > > facilitating a resend that you're likely to see.
> > > > >
> > > > > > I'm sure Johan will do the right thing.
> > > > >
> > > > > My point is that a simple resend has a reasonable chance of getting
> > > > > dropped on the floor.
> > > >
> > > > As I say, I'm sure Johan will do what's required for that not to
> > > > happen.
> > >
> > > Seriously? *Me* do the right thing?
> >
> > Yes, *you*. If a patch slips though a Maintainer's net, which does
> > happen every so often [*], I'm sure even you are not infallible to
> > that, a submitter must issue a RESEND (as you have now just done so).
>
> As you know, five reminders asking for an ack from Mark was sent by the
> two of us combined without even an indication that the messages had been
> noted over a period of almost two months.
>
> If Mark feels that he is getting spammed with unrelated MFD patches,
> then *you* and Mark need to figure out a way to get a message across
> when there actually is something he needs to look at.
>
> I don't care if it's with a special [Lee-wants-Marks-ack] subject
> prefix, an irc message on Linaro's channels or a phone call, but it's not
> something that a patch submitter for MFD should need to know about
> (it obviously isn't even documented).
>
> > > We have a regression in your subsystems (mfd/regulator) with a fix
> > > that's been sitting in both your mailboxes since March 25th.
> >
> > Fully aware and ready to apply once the correct process has been
> > carried out. I get shirty when people submit MFD patches without
> > permission, and I refuse to be a hypocrite.
>
> That's perfectly fine. Your subsystems intersect and you two need to
> figure out how you communicate. That's all.
This issue is out of the ordinary. Normally Mark is pretty good at
providing me with the Acks I need. More commonly I have issues such
as the one you are experiencing with non-responsive/inactive
Maintainers.
In future, for yourself and anyone else who is following this thread
for 'fun', if a patch crosses multiple subsystems (which I try to keep
to a minimum) it's probably best to indicate that in the subject line.
mfd: regulator: <blah>
... would definitely get Marks attention. And yes, I know 'regulator'
is mentioned in the subject line of the particular patch. :)
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-05-18 10:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150325110231.GC10412@localhost>
2015-03-25 11:07 ` [PATCH 1/2] mfd: da9052: fix broken regulator probe Johan Hovold
2015-03-25 11:07 ` [PATCH 2/2] mfd: core: fix platform-device name collisions Johan Hovold
2015-03-25 12:02 ` Bartlomiej Zolnierkiewicz
2015-03-26 8:34 ` Lee Jones
2015-03-25 12:01 ` [PATCH 1/2] mfd: da9052: fix broken regulator probe Bartlomiej Zolnierkiewicz
2015-03-26 8:32 ` Lee Jones
2015-04-14 13:04 ` Johan Hovold
2015-04-29 7:44 ` Johan Hovold
2015-04-29 8:41 ` Lee Jones
2015-05-13 15:43 ` Lee Jones
2015-05-13 16:08 ` Mark Brown
2015-05-13 16:54 ` Lee Jones
2015-05-13 17:29 ` Mark Brown
2015-05-14 7:19 ` Lee Jones
2015-05-15 14:47 ` Johan Hovold
2015-05-18 9:10 ` Lee Jones
2015-05-18 9:51 ` Johan Hovold
2015-05-18 10:13 ` Lee Jones [this message]
2015-05-18 16:28 ` Mark Brown
2015-05-18 16:24 ` Mark Brown
2015-05-18 16:46 ` Johan Hovold
2015-05-18 18:46 ` Mark Brown
2015-05-19 10:01 ` Johan Hovold
2015-05-19 10:38 ` Mark Brown
2015-05-19 11:01 ` Johan Hovold
2015-05-19 12:01 ` Mark Brown
2015-05-15 14:27 ` [PATCH RESEND] " Johan Hovold
2015-05-18 18:47 ` Mark Brown
2015-05-18 18:57 ` Lee Jones
2015-03-30 7:18 ` [PATCH 1/2] " 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=20150518101355.GQ22418@x1 \
--to=lee.jones@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=johan@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=milo.kim@ti.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=support.opensource@diasemi.com \
/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).