RE: [PATCH V2] MAINTAINERS: Add Dialog PMIC search terms for missing documentation and header files
From: Opensource [Steve Twiss]
Date: Wed Jun 08 2016 - 13:32:14 EST
On 08 June 2016 15:19, Mark Brown wrote:
> Subject: Re: [PATCH V2] MAINTAINERS: Add Dialog PMIC search terms for
> missing documentation and header files
>
> 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,
Thanks Mark,
I originally used "Dialog PMIC" in the Subject line to describe the coverage
of MFD, regulator and input/ONKEY. I will be more explicit in future.
> 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@xxxxxxxxxx>
>
> 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.
Lee has since applied PATCH V3 which I resent earlier today. That version finally
removed the regulator files and deleted you from the TO: and CC: e-mail fields
thereby removing you as a dependency.
I will have to send the regulator updates separately at a later date.
In future I will split up the responsibility and define the Subject line better to
remove any ambiguity.
Regards,
Steve