From: Mark Brown <broonie@kernel.org>
To: "Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>
Cc: LINUXKERNEL <linux-kernel@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>,
Support Opensource <Support.Opensource@diasemi.com>
Subject: Re: [PATCH V2] MAINTAINERS: Add Dialog PMIC search terms for missing documentation and header files
Date: Wed, 8 Jun 2016 18:44:18 +0100 [thread overview]
Message-ID: <20160608174418.GO7510@sirena.org.uk> (raw)
In-Reply-To: <6ED8E3B22081A4459DAC7699F3695FB70173DA4272@SW-EX-MBX02.diasemi.com>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-08 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 7:53 Steve Twiss
2016-06-08 14:19 ` Mark Brown
2016-06-08 17:25 ` Opensource [Steve Twiss]
2016-06-08 17:44 ` Mark Brown [this message]
2016-06-09 13:57 ` 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=20160608174418.GO7510@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Support.Opensource@diasemi.com \
--cc=lee.jones@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®