All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Xilinx Zynq changes for v3.18
Date: Fri, 26 Sep 2014 11:32:35 +0200	[thread overview]
Message-ID: <9601562.uSNV2qlMfC@wuerfel> (raw)
In-Reply-To: <542501A1.8020807@monstr.eu>

On Friday 26 September 2014 08:03:13 Michal Simek wrote:
> On 09/25/2014 05:46 PM, Arnd Bergmann wrote:
> > On Tuesday 16 September 2014, Michal Simek wrote:
> >>   git://git.xilinx.com/linux-xlnx.git tags/zynq-cleanup-for-3.18
> >>
> >> for you to fetch changes up to 8097171e19bb69f3e2226827440b71ececa5d74f:
> >>
> >>   ARM: zynq: Remove useless L2C AUX setting (2014-09-16 12:55:12 +0200)
> >>
> >> ----------------------------------------------------------------
> >> arm: Xilinx Zynq cleanup patches for v3.18
> >>
> >> - PM support
> >> - Fix L2 useless setting
> > 
> > I don't see why this counts as cleanup when you add so much more code
> > than you remove, but the individual changes all make sense, so I've
> > pulled it into next/soc.
> 
> What's the branch name for adding new stuff? I see people are using soc.
> 
> 

next/soc is usually for code that is shared by an soc family. Some platforms
also still have board specific files (you dont'), that would go into
next/board.

Ideally all cleanups should come first and get submitted into next/cleanup,
while any other changes that interact with the cleanups can be done on
top of that first branch and merged into the respective topic branches.

	Arnd

      reply	other threads:[~2014-09-26  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 11:07 [GIT PULL] Xilinx Zynq changes for v3.18 Michal Simek
2014-09-25 15:46 ` Arnd Bergmann
2014-09-26  6:03   ` Michal Simek
2014-09-26  9:32     ` Arnd Bergmann [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=9601562.uSNV2qlMfC@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 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.