All of lore.kernel.org
 help / color / mirror / Atom feed
From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 0/2] Sigma Designs Tango4 port
Date: Wed, 23 Dec 2015 15:23:32 +0100	[thread overview]
Message-ID: <567AAE64.8010603@free.fr> (raw)
In-Reply-To: <7h60zqund8.fsf@deeprootsystems.com>

On 22/12/2015 23:31, Kevin Hilman wrote:

> Mason wrote:
> 
>> What is not clear to me is: are you asking me to submit a new defconfig
>> (specific to my platform), or are you saying I need to add the new
>> platform to arch/arm/configs/multi_v7_defconfig
> 
> multi_v7_defconfig, which is what I've been assuming you've been testing
> it with.  Is that correct?

No, I'm not using the Christmas Tree kernel :-)

I needed a small kernel, so I created a config from scratch, just for
my platform (as things were before ARCH_MULTI_V7)

> The latter.  Something like below[1].  Just keep the multi_v7_defconfig
> patch as a separate patch, and we'll take care of the merge conflicts
> when applying to the relevant arm-soc branches.

I'll send the patch ASAP (probably next week).

>> Can I submit the defconfig update as a follow-up patch?
> 
> IMO, it should be part of this series that adds the platform.  That way,
> as soon as it gets merged, it will be automatically build tested by
> various automated builders.  (also note that it would be automatically
> boot tested if I had the hardware as well... hint, hint) ;)

I will contact HQ and ask if they have boards to spare.

Regards.

  parent reply	other threads:[~2015-12-23 14:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15  9:37 [PATCH v11 0/2] Sigma Designs Tango4 port Marc Gonzalez
2015-12-15  9:39 ` [PATCH v11 1/2] arm-soc: Import initial tango4 device tree Marc Gonzalez
2015-12-15  9:41 ` [PATCH v11 2/2] arm-soc: Add support for tango4 platforms Marc Gonzalez
2015-12-22 19:25 ` [PATCH v11 0/2] Sigma Designs Tango4 port Kevin Hilman
2015-12-22 20:23   ` Mason
2015-12-22 20:49     ` Kevin Hilman
2015-12-22 21:57       ` Mason
2015-12-22 22:31         ` Kevin Hilman
2015-12-22 23:58           ` Kevin Hilman
2015-12-23 14:23           ` Mason [this message]
2015-12-22 23:12 ` Olof Johansson
2015-12-23 14:35   ` Mason
2016-01-07  5:08     ` Olof Johansson

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=567AAE64.8010603@free.fr \
    --to=slash.tmp@free.fr \
    --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.