From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm: mediatek: Add more basic features
Date: Fri, 26 Sep 2014 12:11:58 +0200 [thread overview]
Message-ID: <CABuKBeKPmwikra2er4ZMGAPdnbV3zgGSHHi3NsAmij1nkBzHHQ@mail.gmail.com> (raw)
In-Reply-To: <20140924181625.GE19284@localhost>
Hi,
2014-09-24 20:16 GMT+02:00 Olof Johansson <olof@lixom.net>:
> On Mon, Sep 15, 2014 at 05:59:28PM +0200, Matthias Brugger wrote:
>> Hi Arnd and Olof,
>>
>> Please prepare for the next round of Mediatek patches for the mt6589.
>> This patch set adds some minor changes to the Mediatek mt6589 support.
>>
>> Features are low-level debugging on the mt6589, the addition to the
>> "make dtbs" and multi_v7_defconfig,as well as some small changes in
>> the DTS files.
>
> Hi Matthias,
>
> The contents in this branch look OK to me, but I'd prefer to spread them out
> across some of our branches (most of it is DT, one is defconfig and one is soc stuff).
Do you want me to fix the other pull request I send [0]?
As far as I can see, there are three patches for next/soc and the
remaining four for next/dt.
You want me to resend the pull request and split it in two?
[0] http://www.spinics.net/lists/arm-kernel/msg364271.html
>
> Because of this, I've ended up applying patches manually (cherry-picking them out of this branch).
>
> In other words: Code is merged, but branch is not. Thanks!
>
> (Also, we tend to use a capital ARM: as prefix on patch subjects, I fixed that up).
Ok, thanks for the info. If you want me to resend the aforementioned
pull request, I fix that too.
Thanks,
Matthias
>
>
> -Olof
--
motzblog.wordpress.com
prev parent reply other threads:[~2014-09-26 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 15:59 [GIT PULL] arm: mediatek: Add more basic features Matthias Brugger
2014-09-24 18:16 ` Olof Johansson
2014-09-26 10:11 ` Matthias Brugger [this message]
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=CABuKBeKPmwikra2er4ZMGAPdnbV3zgGSHHi3NsAmij1nkBzHHQ@mail.gmail.com \
--to=matthias.bgg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).