Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
	michael@amarulasolutions.com, linux-amarula@amarulasolutions.com,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] configs/at91sam9x5ek_dev_defconfig: add hashes for at91bootstrap3/Linux/headers/u-boot
Date: Wed, 29 May 2024 08:43:27 +0200	[thread overview]
Message-ID: <87le3trucw.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240527160343.2662538-1-dario.binacchi@amarulasolutions.com> (Dario Binacchi's message of "Mon, 27 May 2024 18:03:43 +0200")

>>>>> "Dario" == Dario Binacchi <dario.binacchi@amarulasolutions.com> writes:

 > And enable BR2_DOWNLOAD_FORCE_CHECK_HASHES. With this, we can now drop the
 > defconfig from .checkpackageignore.

 > Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
 > ---
 >  .checkpackageignore                                             | 1 -
 >  .../at91sam9x5ek_dev/patches/at91bootstrap3/at91bootstrap3.hash | 2 ++
 >  .../at91sam9x5ek_dev/patches/linux-headers/linux-headers.hash   | 1 +
 >  board/atmel/at91sam9x5ek_dev/patches/linux/linux.hash           | 2 ++
 >  board/atmel/at91sam9x5ek_dev/patches/uboot/uboot.hash           | 2 ++
 >  configs/at91sam9x5ek_dev_defconfig                              | 1 +
 >  6 files changed, 8 insertions(+), 1 deletion(-)
 >  create mode 100644 board/atmel/at91sam9x5ek_dev/patches/at91bootstrap3/at91bootstrap3.hash
 >  create mode 120000 board/atmel/at91sam9x5ek_dev/patches/linux-headers/linux-headers.hash
 >  create mode 100644 board/atmel/at91sam9x5ek_dev/patches/linux/linux.hash
 >  create mode 100644 board/atmel/at91sam9x5ek_dev/patches/uboot/uboot.hash

We have 4 at91sam9x5ek defconfigs all using the same
at91bootstrap/Linux/U-Boot, so it IMHO would make more sense to put the
patches under board/atmel/at91sam9x5ek/patches and use them from all 4
defconfigs.

Care to send an update doing that? Thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-05-29  6:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 16:03 [Buildroot] [PATCH 1/1] configs/at91sam9x5ek_dev_defconfig: add hashes for at91bootstrap3/Linux/headers/u-boot Dario Binacchi
2024-05-29  6:43 ` Peter Korsgaard [this message]
2024-05-29  6:48   ` Dario Binacchi

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=87le3trucw.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=ludovic.desroches@microchip.com \
    --cc=michael@amarulasolutions.com \
    /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