All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	kvm@vger.kernel.org, pbonzini@redhat.com, lvivier@redhat.com,
	kvm-ppc@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2] MAINTAINERS: Add a section for powerpc
Date: Mon, 25 Apr 2016 14:22:55 +0000	[thread overview]
Message-ID: <20160425142255.GC2386@potion> (raw)
In-Reply-To: <20160422181954.txv4gdtxurifwtob@hawk.localdomain>

2016-04-22 20:19+0200, Andrew Jones:
> On Fri, Apr 22, 2016 at 08:12:54PM +0200, Thomas Huth wrote:
>> +POWERPC
>> +M: Laurent Vivier <lvivier@redhat.com>
>> +M: Thomas Huth <thuth@redhat.com>
>> +L: kvm@vger.kernel.org
>> +L: kvm-ppc@vger.kernel.org
>> +F: powerpc/*
>> +F: lib/powerpc/*
>> +F: lib/ppc64/*
> 
> Looks like MAINTAINERS files usually have the sections in alphabetical
> order (or least the kernel does), so we should probably have put
> POWERPC in between ARM and x86 (and x86 should be X86). But, has a
> MAINTAINERS file update ever gone to a v3 :-)?

I can (and will if you don't protest) change that before pushing.

>                                                         But, has a
> MAINTAINERS file update ever gone to a v3 :-)?

(And we could ask to change the heading to "PowerPC" for v4. :])

WARNING: multiple messages have this Message-ID (diff)
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	kvm@vger.kernel.org, pbonzini@redhat.com, lvivier@redhat.com,
	kvm-ppc@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2] MAINTAINERS: Add a section for powerpc
Date: Mon, 25 Apr 2016 16:22:55 +0200	[thread overview]
Message-ID: <20160425142255.GC2386@potion> (raw)
In-Reply-To: <20160422181954.txv4gdtxurifwtob@hawk.localdomain>

2016-04-22 20:19+0200, Andrew Jones:
> On Fri, Apr 22, 2016 at 08:12:54PM +0200, Thomas Huth wrote:
>> +POWERPC
>> +M: Laurent Vivier <lvivier@redhat.com>
>> +M: Thomas Huth <thuth@redhat.com>
>> +L: kvm@vger.kernel.org
>> +L: kvm-ppc@vger.kernel.org
>> +F: powerpc/*
>> +F: lib/powerpc/*
>> +F: lib/ppc64/*
> 
> Looks like MAINTAINERS files usually have the sections in alphabetical
> order (or least the kernel does), so we should probably have put
> POWERPC in between ARM and x86 (and x86 should be X86). But, has a
> MAINTAINERS file update ever gone to a v3 :-)?

I can (and will if you don't protest) change that before pushing.

>                                                         But, has a
> MAINTAINERS file update ever gone to a v3 :-)?

(And we could ask to change the heading to "PowerPC" for v4. :])

  reply	other threads:[~2016-04-25 14:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 18:12 [kvm-unit-tests PATCH v2] MAINTAINERS: Add a section for powerpc Thomas Huth
2016-04-22 18:12 ` Thomas Huth
2016-04-22 18:19 ` Andrew Jones
2016-04-22 18:19   ` Andrew Jones
2016-04-25 14:22   ` Radim Krčmář [this message]
2016-04-25 14:22     ` Radim Krčmář
2016-04-23  8:09 ` Laurent Vivier
2016-04-23  8:09   ` Laurent Vivier
2016-04-25 15:28 ` Radim Krčmář
2016-04-25 15:28   ` Radim Krčmář

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=20160425142255.GC2386@potion \
    --to=rkrcmar@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=lvivier@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=thuth@redhat.com \
    /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.