All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] sunxi: Sync dts files with the upstream kernel
Date: Tue, 15 Mar 2016 11:14:35 +0100	[thread overview]
Message-ID: <56E7E08B.1050505@redhat.com> (raw)
In-Reply-To: <1458034168.1643.4.camel@hellion.org.uk>

Hi,

On 15-03-16 10:29, Ian Campbell wrote:
> On Mon, 2016-03-14 at 21:49 +0100, Hans de Goede wrote:
>> Sync dts files with the upstream kernel including
>> changes queued for 4.6:
>>
>> https://git.kernel.org/cgit/linux/kernel/git/mripard/linux.git/commit/?h=sunxi/dt-for-4.6
>>
>> Note this adds a number of new unused board dts files. I've asked the
>> authors of the kernel commits adding these to submit a matching defconfig
>> to u-boot.
>>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>
> Both patches here: Acked-by: Ian Campbell <ijc@hellion.org.uk>

Thanks.

> Do you have a script or something which (semi-)automates these imports,
> or is it manual faff each time?

Manual, it is not that much work, just cp the files over since we are
using pristine kernel files with no u-boot specific mods.

Then git add all of them, and do a commit, in the commit msg editor
look at the list of "new file"'s, add those to the Makefile and then
commit the Makefile as a fixup.

Starting with this sync I also lookup the first kernel commit of any
new dts files (not dtsi files only dts files) and then send a mail
to the committer asking them to submit a matching u-boot defconfig.

Regards,

Hans

  reply	other threads:[~2016-03-15 10:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 20:49 [U-Boot] [PATCH 1/2] sunxi: Sync dts files with the upstream kernel Hans de Goede
2016-03-14 20:49 ` [U-Boot] [PATCH 2/2] sunxi: Add defconfig and dts for the Polaroid MID2809PXE4 tablet Hans de Goede
2016-03-15  9:29 ` [U-Boot] [PATCH 1/2] sunxi: Sync dts files with the upstream kernel Ian Campbell
2016-03-15 10:14   ` Hans de Goede [this message]
2016-03-15 14:29 ` Peter Korsgaard

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=56E7E08B.1050505@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=u-boot@lists.denx.de \
    /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.