public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: khilman@kernel•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v11 0/2] Sigma Designs Tango4 port
Date: Tue, 22 Dec 2015 15:58:32 -0800	[thread overview]
Message-ID: <7hy4cmrq6v.fsf@deeprootsystems.com> (raw)
In-Reply-To: <7h60zqund8.fsf@deeprootsystems.com> (Kevin Hilman's message of "Tue, 22 Dec 2015 14:31:15 -0800")

Kevin Hilman <khilman@kernel•org> writes:

> Mason <slash.tmp@free•fr> writes:

[...]

>>
>> 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) ;)

Olof's and my emails crossed paths, so the main part of the series is
already merged.

Please send a defconfig patch which we can apply to next/defconfig and
so it gets some build test coverage.

Thanks,

Kevin

  reply	other threads:[~2015-12-22 23:58 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 [this message]
2015-12-23 14:23           ` Mason
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=7hy4cmrq6v.fsf@deeprootsystems.com \
    --to=khilman@kernel$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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