Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 02/11] Add Linux Kernel stable 4.4.16 patch file for Arietta G25
Date: Sun, 18 Sep 2016 20:02:07 +0200	[thread overview]
Message-ID: <20160918200207.75421760@free-electrons.com> (raw)
In-Reply-To: <1470827167-9426-4-git-send-email-biagio.hkr@gmail.com>

Hello,

On Wed, 10 Aug 2016 13:05:58 +0200, Biagio Montaruli wrote:
> Signed-off-by: Biagio Montaruli <biagio.hkr@gmail.com>
> ---
>  .../patches/linux/linux-4.4.16-arietta.patch       | 409 +++++++++++++++++++++
>  1 file changed, 409 insertions(+)
>  create mode 100644 board/acmesystems/arietta-g25/patches/linux/linux-4.4.16-arietta.patch

Is there a good motivation to use the 4.4 kernel that requires some
patches to support the Arietta, as opposed to using the mainline kernel
which has support for this platform built-in?

Also, if you really insist in using the 4.4 kernel, in PATCH 05/11,
you're making the defconfig point to your own Github repository for the
kernel. Why don't you include the necessary patches in your Github
repository, then?


> +diff --git a/arch/arm/configs/acme-arietta_defconfig b/arch/arm/configs/acme-arietta_defconfig
> +new file mode 100644
> +index 0000000..b014260
> +--- /dev/null
> ++++ b/arch/arm/configs/acme-arietta_defconfig

Do we really need an entirely new defconfig? What about using the
at91_dt_defconfig available in the kernel?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-09-18 18:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 11:05 [Buildroot] Patches for Acme Systems Arietta G25 and Aria G25 Biagio Montaruli
2016-08-10 11:05 ` [Buildroot] [PATCH 00/11] Series of patch to improve Buildroot configuration for Biagio Montaruli
2016-09-18 17:59   ` Thomas Petazzoni
2016-08-10 11:05 ` [Buildroot] [PATCH 01/11] Update genimage configuration file for Arietta-G25 in order to build a bootable SD card image named "sdcard.img" Biagio Montaruli
2016-09-18 18:00   ` Thomas Petazzoni
2016-08-10 11:05 ` [Buildroot] [PATCH 02/11] Add Linux Kernel stable 4.4.16 patch file for Arietta G25 Biagio Montaruli
2016-09-18 18:02   ` Thomas Petazzoni [this message]
2016-09-18 18:21     ` Thomas Petazzoni
2016-08-10 11:05 ` [Buildroot] [PATCH 03/11] Add post-build.sh script " Biagio Montaruli
2016-09-18 18:04   ` Thomas Petazzoni
2016-08-10 11:06 ` [Buildroot] [PATCH 04/11] Add root filesystem overlay files and directories " Biagio Montaruli
2016-09-18 18:05   ` Thomas Petazzoni
2016-08-10 11:06 ` [Buildroot] [PATCH 05/11] Update and improve default configuration files for Arietta G25 (both 128MB and 256MB version) Biagio Montaruli
2016-09-18 18:07   ` Thomas Petazzoni
2016-08-10 11:06 ` [Buildroot] [PATCH 06/11] Update README file for Arietta G25 named "readme.txt" Biagio Montaruli
2016-08-10 11:06 ` [Buildroot] [PATCH 07/11] Add Linux Kernel stable v4.4.16 patch file for Aria G25 Biagio Montaruli
2016-09-18 18:09   ` Thomas Petazzoni
2016-08-10 11:06 ` [Buildroot] [PATCH 08/11] Add post-build.sh script " Biagio Montaruli
2016-08-10 11:06 ` [Buildroot] [PATCH 09/11] Update genimage configuration file and add post-image.sh script for Aria G25 in order to build a bootable SD card image named "sdcard.img" Biagio Montaruli
2016-08-10 11:06 ` [Buildroot] [PATCH 10/11] Update and improve default configuration files for Arietta G25 (both 128MB and 256MB version) Biagio Montaruli
2016-08-10 11:06 ` [Buildroot] [PATCH 11/11] Update README file for Aria G25 named "readme.txt" Biagio Montaruli

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=20160918200207.75421760@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox