All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: "Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>,
	LINUXKERNEL <linux-kernel@vger.kernel.org>,
	Support Opensource <Support.Opensource@diasemi.com>
Subject: Re: [PATCH V2] MAINTAINERS: Add Dialog PMIC search terms for missing documentation and header files
Date: Thu, 9 Jun 2016 14:57:21 +0100	[thread overview]
Message-ID: <20160609135721.GC2385@dell> (raw)
In-Reply-To: <20160608174418.GO7510@sirena.org.uk>

On Wed, 08 Jun 2016, Mark Brown wrote:
> On Wed, Jun 08, 2016 at 05:25:30PM +0000, Opensource [Steve Twiss] wrote:
> > On 08 June 2016 15:19, Mark Brown wrote:
> 
> > > We *really* shouldn't be blocking on my ack for trivial changes outside
> > > the subsystem like this though :(
> 
> > There had been no reply since my first e-mail round about a month ago, so I
> > figured there was something wrong with the patch submission.
> 
> It was the activity pattern on the patch more than anything else, and of
> course the merge window was in that month as well.
> 
> > In future I will split up the responsibility and define the Subject line better to
> > remove any ambiguity.
> 
> Like I say a trivial maintainers update like this really should just get
> applied anyway.

Right.  I was about to apply this regardless.

The issue was not specific to this patch. I tend to go dark during
the merge-window to concentrate on my 'real job' (TM).  I applied your
other patch because it's the one I came across first.  This one was
marked as "to review" (as I am doing now).

Don't worry about splitting, I will apply this and remove the other.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2016-06-09 13:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24  7:53 [PATCH V2] MAINTAINERS: Add Dialog PMIC search terms for missing documentation and header files Steve Twiss
2016-06-08 14:19 ` Mark Brown
2016-06-08 17:25   ` Opensource [Steve Twiss]
2016-06-08 17:44     ` Mark Brown
2016-06-09 13:57       ` Lee Jones [this message]

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=20160609135721.GC2385@dell \
    --to=lee.jones@linaro.org \
    --cc=Support.Opensource@diasemi.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stwiss.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 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.