mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: 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 15:19:11 +0100	[thread overview]
Message-ID: <20160608141911.GK7510@sirena.org.uk> (raw)
In-Reply-To: <20160524081038.85F443FAAB@swsrvapps-01.diasemi.com>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

On Tue, May 24, 2016 at 08:53:46AM +0100, Steve Twiss wrote:

> The majority of these updates are for MFD documentation and headers,
> although there is a mixture with the regulators as well.

> I previously send a patch TO: Lee and CC:'ed Mark, but I think now I
> need to resend V2 with Mark in the TO: field.
> https://lkml.org/lkml/2016/5/11/419

No, the issue here is that this is MFD patch with a non-obvious subject
line, it's getting a lot of new versions (which usually indicates that
there's stuff going on and it might well change again quickly) and it's
getting replies (which would normally suggest it's being taken care of
or needs more revision).  This all means that it looks like something
best left for later.

> I have also updated this V2 patch to align with linux-next/v4.6
> and removed the change to the onkey driver.

> Lee: with Mark's Ack, would it be possible for you to take these
> through please?

Acked-by: Mark Brown <broonie@kernel.org>

We *really* shouldn't be blocking on my ack for trivial changes outside
the subsystem like this though :(

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-06-08 14:19 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 [this message]
2016-06-08 17:25   ` Opensource [Steve Twiss]
2016-06-08 17:44     ` Mark Brown
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=20160608141911.GK7510@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stwiss.opensource@diasemi.com \
    --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

all inboxes | Powered by JetHome®