All of lore.kernel.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: bcm2835: Move to mach-bcm directory
Date: Fri, 21 Feb 2014 10:48:35 -0700	[thread overview]
Message-ID: <53079173.3030305@wwwdotorg.org> (raw)
In-Reply-To: <CAPdLdqmX7xYwHse4y9+2_-491pw0ODcjxou6_ZC9=aoiR72-MQ@mail.gmail.com>

On 02/21/2014 10:41 AM, Markus Mayer wrote:
> On 21 February 2014 06:09, Matt Porter <mporter@linaro.org> wrote:
>> On Thu, Feb 20, 2014 at 09:53:56PM -0700, Stephen Warren wrote:
>>> On 02/20/2014 05:16 PM, Markus Mayer wrote:
>>>> Move the bcm2835 board file into the mach-bcm directory. This allows us
>>>> to get rid of the mach-bcm2835 directory with the associated Kconfig
>>>> and Makefile.
>>>
>>> This looks fine, although it needs a small patch to bcm2835_defconfig
>>> squashed in, which I'll post in a second.
>>>
>>> Do you want me to take it through the bcm2835 tree? That's probably
>>> easiest to avoid conflicts with any other bcm2835 patches, not that it's
>>> too likely there will be any to the board file.
>>
>> That's ok with me. Be aware that we may have minor Kconfig/Makefile
>> conflicts between the bcm2835 tree and the mach-bcm tree since we just
>> queued the bcm5301x support.
> 
> Matt, will you squash Stephen's patch into mine when you take the
> patches or should I submit a v2 of the patch that combines both?

I think Matt said it was OK to take them through the bcm2835 tree. I'll
squash them together; no need to repost.

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Markus Mayer <markus.mayer@linaro.org>, Matt Porter <mporter@linaro.org>
Cc: Christian Daudt <bcm@fixthebug.org>,
	ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: bcm2835: Move to mach-bcm directory
Date: Fri, 21 Feb 2014 10:48:35 -0700	[thread overview]
Message-ID: <53079173.3030305@wwwdotorg.org> (raw)
In-Reply-To: <CAPdLdqmX7xYwHse4y9+2_-491pw0ODcjxou6_ZC9=aoiR72-MQ@mail.gmail.com>

On 02/21/2014 10:41 AM, Markus Mayer wrote:
> On 21 February 2014 06:09, Matt Porter <mporter@linaro.org> wrote:
>> On Thu, Feb 20, 2014 at 09:53:56PM -0700, Stephen Warren wrote:
>>> On 02/20/2014 05:16 PM, Markus Mayer wrote:
>>>> Move the bcm2835 board file into the mach-bcm directory. This allows us
>>>> to get rid of the mach-bcm2835 directory with the associated Kconfig
>>>> and Makefile.
>>>
>>> This looks fine, although it needs a small patch to bcm2835_defconfig
>>> squashed in, which I'll post in a second.
>>>
>>> Do you want me to take it through the bcm2835 tree? That's probably
>>> easiest to avoid conflicts with any other bcm2835 patches, not that it's
>>> too likely there will be any to the board file.
>>
>> That's ok with me. Be aware that we may have minor Kconfig/Makefile
>> conflicts between the bcm2835 tree and the mach-bcm tree since we just
>> queued the bcm5301x support.
> 
> Matt, will you squash Stephen's patch into mine when you take the
> patches or should I submit a v2 of the patch that combines both?

I think Matt said it was OK to take them through the bcm2835 tree. I'll
squash them together; no need to repost.

  reply	other threads:[~2014-02-21 17:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21  0:16 [PATCH] ARM: bcm2835: Move to mach-bcm directory Markus Mayer
2014-02-21  0:16 ` Markus Mayer
2014-02-21  4:53 ` Stephen Warren
2014-02-21  4:53   ` Stephen Warren
2014-02-21 14:09   ` Matt Porter
2014-02-21 14:09     ` Matt Porter
2014-02-21 17:41     ` Markus Mayer
2014-02-21 17:41       ` Markus Mayer
2014-02-21 17:48       ` Stephen Warren [this message]
2014-02-21 17:48         ` Stephen Warren
2014-02-21 17:50       ` Matt Porter
2014-02-21 17:50         ` Matt Porter
2014-02-25  2:49 ` Stephen Warren
2014-02-25  2:49   ` Stephen Warren

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=53079173.3030305@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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.