From: John Crispin <blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH V7 1/2] regulator: Add document for MT6323 regulator
Date: Fri, 26 Feb 2016 15:58:30 +0100 [thread overview]
Message-ID: <56D06816.7070709@openwrt.org> (raw)
In-Reply-To: <3623271.aQ3n624Sax@wuerfel>
On 26/02/2016 15:22, Arnd Bergmann wrote:
> On Monday 22 February 2016 13:56:56 John Crispin wrote:
>> Signed-off-by: John Crispin <blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
>> Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> ---
>> This patch needs to be merged post-rc1 as it depends on the MFD series of
>> the PMIC which is already inside Lee's tree pending the PR.
>
> (dropping most lists)
>
> Hi John,
>
> Do you or someone else have a git tree that has all the remaining
> patches for mt6323 that need to be merged?
>
> We are doing a code review session at Linaro Connect and it seems
> like a nice platform to include, given that it is simpler than
> most of the phone oriented platforms that have lots of complex
> code out of tree.
>
> Arnd
>
Hi Arnd,
sure thing i can get one online for you in the next 48 hours, including
all the patches required to boot mt7623 with v4.4. I still have a few
outdated patches in my local tree for the scpsys and usb part, so I need
to extract latest versions from the ML.
would v4.4 be ok or do you prefer me using the latest rc ?
And yes it is a nice platform, had a fun time making it all work. Can't
wait to get the first off the shelf CPEs that i can support in OpenWrt.
John
next prev parent reply other threads:[~2016-02-26 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 12:56 [PATCH V7 1/2] regulator: Add document for MT6323 regulator John Crispin
2016-02-22 12:56 ` [PATCH V7 2/2] regulator: mt6323: Add support " John Crispin
[not found] ` <1456145817-12741-1-git-send-email-blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2016-02-26 14:22 ` [PATCH V7 1/2] regulator: Add document " Arnd Bergmann
2016-02-26 14:58 ` John Crispin [this message]
[not found] ` <56D06816.7070709-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2016-02-26 15:16 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2016-02-25 10:37 John Crispin
2016-03-02 18:07 ` Rob Herring
2016-03-02 18:11 ` John Crispin
2016-03-02 18:13 ` John Crispin
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=56D06816.7070709@openwrt.org \
--to=blogic-p3rkhjxn3npafugrpc6u6w@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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