linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 2/4] [ARM] mmp: support marvell ARMADA610
Date: Tue, 5 Jan 2010 04:13:41 -0500	[thread overview]
Message-ID: <771cded01001050113y44551a12i7a03009f62108f8@mail.gmail.com> (raw)
In-Reply-To: <f17812d71001042330p21da40dcr7b29a1316cf9a615@mail.gmail.com>

On Tue, Jan 5, 2010 at 2:30 AM, Eric Miao <eric.y.miao@gmail.com> wrote:
>> OK. Update the patches.
>>
>
> Applied to branch 'mmp2' and made some changes as follows
> (please let me know your concerns and help test this):
>
> 1. irq-mmp2.c: separate the difference into different irq_chip
> and individual demux handler for those MUXed IRQs, naming
> is changed a bit as well. Having a single irq_chip and demux
> handler isn't performance friendly - having to go through a lengthy
> condition branches each time - and that's why irq_chip is invented.
>
> 2. merge patch 1, 2, 3 together so mmp2 can build (my build
> here complains about no machine_desc defined if flint support
> isn't there)
>
> And I'd like you to help co-maintaine MMP2 together with me,
> please kindly Ack if you're fine with the patch follows:
>
> commit 2004b15682f0f612b85088d730164e91fca2eec8
> Author: Eric Miao <eric.y.miao@gmail.com>
> Date: ? Tue Jan 5 15:28:26 2010 +0800
>
> ? ?MAINTAINERS: add maintainers for Marvell MMP2 (aka ARMADA610) support
>
> ? ?Cc: Haojian Zhuang <haojian.zhuang@marvell.com>
> ? ?Signed-off-by: Eric Miao <eric.y.miao@gmail.com>
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 66f5f7d..33978ed 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4439,6 +4439,13 @@ L: ? ? ? linux-arm-kernel at lists.infradead.org
> (moderated for non-subscribers)
> ?T: ? ? git git://git.kernel.org/pub/scm/linux/kernel/git/ycmiao/pxa-linux-2.6.git
> ?S: ? ? Maintained
>
> +MMP2 SUPPORT (aka ARMADA610)
> +M: ? ? Haojian Zhuang <haojian.zhuang@marvell.com>
> +M: ? ? Eric Miao <eric.y.miao@gmail.com>
> +L: ? ? linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
> +T: ? ? git git://git.kernel.org/pub/scm/linux/kernel/git/ycmiao/pxa-linux-2.6.git
> +S: ? ? Maintained
> +
> ?PXA MMCI DRIVER
> ?S: ? ? Orphan
>

Acked.

Best Regards
Haojian

  reply	other threads:[~2010-01-05  9:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07  6:19 [patch 2/4] [ARM] mmp: support marvell ARMADA610 Haojian Zhuang
2009-12-29  3:49 ` Eric Miao
2009-12-31 14:42   ` Haojian Zhuang
2010-01-01  3:46     ` Eric Miao
2010-01-04  2:27       ` Haojian Zhuang
2010-01-04  2:49         ` Eric Miao
2010-01-04  3:29           ` Haojian Zhuang
2010-01-04  4:27             ` Eric Miao
2010-01-04 10:15               ` Haojian Zhuang
2010-01-04 10:27                 ` Russell King - ARM Linux
2010-01-04 11:16                   ` Haojian Zhuang
2010-01-05  7:30                     ` Eric Miao
2010-01-05  9:13                       ` Haojian Zhuang [this message]
2010-01-05  9:34                         ` Eric Miao
2010-01-04 10:30           ` Russell King - ARM Linux

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=771cded01001050113y44551a12i7a03009f62108f8@mail.gmail.com \
    --to=haojian.zhuang@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).