linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: multi_v7_defconfig: Replace USB_RCAR_GEN2_PHY by PHY_RCAR_GEN2
Date: Tue, 12 May 2015 21:42:40 +0200	[thread overview]
Message-ID: <2579991.7Fqv0Atap3@wuerfel> (raw)
In-Reply-To: <CAMuHMdU9363XjsEGNmy8CyLL6OR91khWFGQjn72qwWLr9=J1cQ@mail.gmail.com>

On Tuesday 12 May 2015 18:30:59 Geert Uytterhoeven wrote:
> 
> I think Simon's question was more about asking what's the proper process
> for updating multi_v7_defconfig.
> 
> Should this go through you / arm at kernel.org directly?
> Should it go through arm subarchitecture maintainers, causing merge conflicts?

I think it should go through subarch maintainers, and we'll handle the
conflicts as they arise when merging into the next/defconfig branch.
This does mean that it's important to send the defconfig changes separately
from other changes if possible, but it's fine to have a branch that touches
both platform-specific and generic defconfig files.

> BTW, arm at kernel.org isn't documented in MAINTAINERS.

Right, that is intentional. We don't want to get Cc'd on 4000 patches per
month that get sent to the mailing list for mach-*. By having a maintainer
for each subdirectory and letting them decide what to forward to us,
we're able to do our job better.

	Arnd

  reply	other threads:[~2015-05-12 19:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 12:08 [PATCH 1/2] ARM: shmobile: defconfig: Replace USB_RCAR_GEN2_PHY by PHY_RCAR_GEN2 Geert Uytterhoeven
2015-04-28 12:08 ` [PATCH 2/2] ARM: multi_v7_defconfig: " Geert Uytterhoeven
2015-04-30  0:17   ` Simon Horman
2015-05-09  2:14     ` Simon Horman
2015-05-12 15:15       ` Arnd Bergmann
2015-05-12 16:30         ` Geert Uytterhoeven
2015-05-12 19:42           ` Arnd Bergmann [this message]
2015-05-13  0:19             ` Simon Horman
2015-04-30  0:19 ` [PATCH 1/2] ARM: shmobile: defconfig: " Simon Horman

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=2579991.7Fqv0Atap3@wuerfel \
    --to=arnd@arndb.de \
    --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).