All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V2 0/7] linux and uboot version bumps and cleanup
Date: Wed, 10 Apr 2019 13:41:46 +0200	[thread overview]
Message-ID: <20190410134146.51426682@windsurf.home> (raw)
In-Reply-To: <20190409154503.7598-1-shyam.saini@amarulasolutions.com>

Hello Shyam,

On Tue,  9 Apr 2019 21:14:56 +0530
Shyam Saini <shyam.saini@amarulasolutions.com> wrote:

> - Logically reorder all nanopi m1 plus patches  
> - Remove BR2_GLOBAL_PATCH_DIR option from nanopi_m1_plus_defconfig
> 
> Shyam Saini (7):
>   configs: pine64_sopine: Bump to the linux 5.0 and u-boot 2019.01
>   configs: orangepi_prime: Bump to the linux 5.0 and u-boot 2019.01
>   configs: olimex_a64_olinuxino: Bump to the linux 5.0 and u-boot
>     2019.01
>   configs: orangepi_plus: Bump to the linux 5.0 and u-boot 2019.01
>   configs: nanopi_m1: Bump to the linux 5.0 and u-boot 2019.01
>   configs: nanopi_m1_plus: Bump to the linux 5.0 and u-boot 2019.01
>   board: friendlyarm: nanopi-m1-plus: patches: Remove linux patch

This was still wrong: if I apply the first 6 patches but not the last
one, the nanopi_m1_plus defconfig is broken: you try to build Linux 5.0
but apply a patch that was made for Linux 4.13. The last two patches
should have been squashed together to form a single patch.

Also, the commit title prefix should follow the format
"configs/<configname>".

I have fixed those issues and applied. Thanks!

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2019-04-10 11:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 15:44 [Buildroot] [V2 0/7] linux and uboot version bumps and cleanup Shyam Saini
2019-04-09 15:44 ` [Buildroot] [V2 1/7] configs: pine64_sopine: Bump to the linux 5.0 and u-boot 2019.01 Shyam Saini
2019-04-09 15:44 ` [Buildroot] [V2 2/7] configs: orangepi_prime: " Shyam Saini
2019-04-09 15:44 ` [Buildroot] [V2 3/7] configs: olimex_a64_olinuxino: " Shyam Saini
2019-04-09 15:45 ` [Buildroot] [V2 4/7] configs: orangepi_plus: " Shyam Saini
2019-04-09 15:45 ` [Buildroot] [V2 5/7] configs: nanopi_m1: " Shyam Saini
2019-04-09 15:45 ` [Buildroot] [V2 6/7] configs: nanopi_m1_plus: " Shyam Saini
2019-04-09 15:45 ` [Buildroot] [V2 7/7] board: friendlyarm: nanopi-m1-plus: patches: Remove linux patch Shyam Saini
2019-04-10 11:41 ` Thomas Petazzoni [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=20190410134146.51426682@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.