From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Initial OLPC XO-1.75/XO-4 support
Date: Tue, 02 Jul 2013 09:35:01 -0700 [thread overview]
Message-ID: <20130702163501.10823.57484@quantum> (raw)
In-Reply-To: <CAMLZHHQu_UUQvT1db7hL2XYX=EzwNaGjyeTuZkwfYHJmG5BUdA@mail.gmail.com>
Quoting Daniel Drake (2013-07-02 07:26:22)
> On Mon, Jul 1, 2013 at 10:53 PM, Olof Johansson <olof@lixom.net> wrote:
> > 1) Please post the drivers/clk patches to mturquette. THey don't look dependent
> > on the rest of the patches, just general improvements and cleanups.
> > 2) I really wish there was a generic catch-all compat for the boards, so we
> > didn't have to modify mmp2-dt.c for every new board added -- it really
> > defies the purpose of only changing the data you pass into the kernel. This
> > is mostly something for Eric/Haojian to sort out though.
> > 3) Please post the patches as a series instead of a pull request, given that
> > they should probably take different paths up the tree (clk vs the platform,
> > etc). You should at least get review/acked-by of the clk pieces from Mike
> > Turquette.
>
> Thanks for the suggestions. I have already posted the patches as
> emails a little more than 2 weeks ago, including sending the clock
> ones to Mike. I will resend next week if they are still pending, when
> the maintainers might be a bit less busy.
I saw the MMP patches but they were too late for me to take into
clk-next towards 3.11. When this happens I usually email the patch
author privately and let them know that I will take a look after the
merge window but I forgot to send you that email.
Regards,
Mike
>
> cheers
> Daniel
prev parent reply other threads:[~2013-07-02 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 3:12 [GIT PULL] Initial OLPC XO-1.75/XO-4 support Daniel Drake
2013-07-02 4:53 ` Olof Johansson
2013-07-02 14:26 ` Daniel Drake
2013-07-02 16:35 ` Mike Turquette [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=20130702163501.10823.57484@quantum \
--to=mturquette@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.