All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Mark Langsdorf <mark.langsdorf@calxeda.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	aliguori@us.ibm.com, qemu-devel@nongnu.org,
	paul@codesourcery.com
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: Add hw/highbank.c maintainer
Date: Sat, 04 Feb 2012 12:41:54 +0100	[thread overview]
Message-ID: <4F2D1982.7000305@suse.de> (raw)
In-Reply-To: <CAFEAcA_RXRjRAP8bu9evzudJJmPWcFQXEfR+SsPJtzdbFT+1Bg@mail.gmail.com>

Am 04.02.2012 03:43, schrieb Peter Maydell:
> On 3 February 2012 20:58, Mark Langsdorf <mark.langsdorf@calxeda.com> wrote:
>> Signed-off-by: Mark Langsdorf <mark.langsdorf@calxeda.com>
>> ---
>>  MAINTAINERS |    5 +++++
>>  1 files changed, 5 insertions(+), 0 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 173e893..bdc254f 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -237,6 +237,11 @@ M: Peter Maydell <peter.maydell@linaro.org>
>>  S: Maintained
>>  F: hw/versatilepb.c
>>
>> +Calxeda Highbank
>> +M: Mark Langsdorf <mark.langsdorf@calxeda.com>
>> +S: Supported
>> +F: hw/highbank.c
>> +
> 
> Thanks for submitting this. I think your entry should go at the top, above
> 'Gumstix', since we seem to be sorting the subsections alphabetically
> by heading.

For PowerPC we've started adding the board-specific device files as
well, so that they get a maintainer associated. I vaguely remember
there's more files than just highbank.c.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2012-02-04 11:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 20:58 [Qemu-devel] [PATCH] MAINTAINERS: Add hw/highbank.c maintainer Mark Langsdorf
2012-02-04  2:43 ` Peter Maydell
2012-02-04 11:41   ` Andreas Färber [this message]
2012-02-06 14:05 ` [Qemu-devel] [PATCH v2] " Mark Langsdorf
2012-02-15 15:34   ` Peter Maydell

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=4F2D1982.7000305@suse.de \
    --to=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=mark.langsdorf@calxeda.com \
    --cc=paul@codesourcery.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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.