From: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Steve Twiss <stwiss.opensource-WBD+wuPFNBhBDgjK7y7TUQ@public.gmane.org>
Cc: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
LINUX-KERNEL
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
DEVICETREE <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Dmitry Torokhov
<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Eduardo Valentin
<edubezval-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
LINUX-INPUT <linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
LINUX-PM <linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
LINUX-WATCHDOG
<linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Support Opensource
<Support.Opensource-WBD+wuPFNBhBDgjK7y7TUQ@public.gmane.org>,
Wim Van Sebroeck <wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.org>,
Zhang Rui <rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [RESEND PATCH V7 5/7] regulator: da9061: BUCK and LDO regulator driver
Date: Wed, 24 May 2017 09:40:49 +0100 [thread overview]
Message-ID: <20170524084049.iy4dlrbmkzsqjvav@dell> (raw)
In-Reply-To: <6ED8E3B22081A4459DAC7699F3695FB7018CD8D651-68WUHU125fLzLL1Oxlh9IgLouzNaz+3S@public.gmane.org>
On Wed, 24 May 2017, Steve Twiss wrote:
> On 23 May 2017 18:17 Mark Brown
> > To: Steve Twiss
> > Subject: Re: [RESEND PATCH V7 5/7] regulator: da9061: BUCK and LDO regulator driver
> >
> > On Tue, May 23, 2017 at 02:40:45PM +0100, Steve Twiss wrote:
> >
> > > This patch was Acked by Mark Brown, a long time ago, way back in Oct 2016
> > > (https://patchwork.kernel.org/patch/9397787/).
> > > I have kept Mark Brown's Ack attached because there have been no real
> > > code changes since then, but I have recently updated the copyright header
> > > slightly, rebased the code (no changes necessary) and compile tested it
> > > against x86_64.
> >
> > > The MFD files which this patch depended on were accepted into linux-next
> > > by Lee Jones last week. If there is anything in the way of this patch
> > > acceptance, could you please let me know?
> >
> > Given that I've acked this and it depends on the MFD changes I'd have
> > expected Lee to apply it. If nothing else happens I can apply it after
> > the next merge window, otherwise either Lee needs to send me a pull
> > request for the MFD change so I've got the dependency or he needs to
> > apply this.
>
> Hi Mark,
>
> Thanks,
> No problem, just some minor administration.
>
> @Lee
> Could you please send Mark a pull request for the regulator component to the
> DA9062/61 changes [PATCH V7 5/7] regulator: da9061: BUCK and LDO regulator
> driver.
That wasn't one of the options. ;)
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-24 8:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1495546845.git.stwiss.opensource@diasemi.com>
2017-05-23 13:40 ` [RESEND PATCH V7 7/7] MAINTAINERS: da9062/61 updates to the Dialog Semiconductor search terms Steve Twiss
2017-05-23 14:04 ` Guenter Roeck
2017-05-30 9:09 ` Lee Jones
[not found] ` <cover.1495546845.git.stwiss.opensource-WBD+wuPFNBhBDgjK7y7TUQ@public.gmane.org>
2017-05-23 13:40 ` [RESEND PATCH V7 5/7] regulator: da9061: BUCK and LDO regulator driver Steve Twiss
2017-05-23 17:17 ` Mark Brown
2017-05-24 8:12 ` Steve Twiss
[not found] ` <6ED8E3B22081A4459DAC7699F3695FB7018CD8D651-68WUHU125fLzLL1Oxlh9IgLouzNaz+3S@public.gmane.org>
2017-05-24 8:40 ` Lee Jones [this message]
[not found] ` <20170523171721.lpqjhakaawnz4prz-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2017-05-24 8:32 ` Lee Jones
2017-05-24 10:10 ` Mark Brown
[not found] ` <20170524101057.v2fqwki4fopx5k7y-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2017-05-30 9:17 ` Lee Jones
2017-06-06 19:02 ` Mark Brown
[not found] <cover.1496823229.git.stwiss.opensource@diasemi.com>
2017-06-07 8:13 ` Steve Twiss
2017-06-07 9:41 ` Mark Brown
2017-06-07 14:09 ` Steve Twiss
2017-06-07 15:42 ` Mark Brown
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=20170524084049.iy4dlrbmkzsqjvav@dell \
--to=lee.jones-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=Support.Opensource-WBD+wuPFNBhBDgjK7y7TUQ@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=edubezval-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=stwiss.opensource-WBD+wuPFNBhBDgjK7y7TUQ@public.gmane.org \
--cc=wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.org \
/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