Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] defconfig for warpboard
Date: Sun, 21 Jun 2015 15:32:36 +0200	[thread overview]
Message-ID: <5586BCF4.4070405@mind.be> (raw)
In-Reply-To: <20150621005619.GC23827@arthur-debian>

On 06/21/15 02:56, Arthur LAMBERT wrote:
> Le Friday 19 Jun 2015 ?? 23:48:57 (+0200), Arnout Vandecappelle a ?crit :
>> On 06/19/15 17:29, Arthur LAMBERT wrote:
[snip]
>>> +BR2_LINUX_KERNEL_PATCH="board/freescale/warpboard/linux/"
>>> +BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
>>> +BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/freescale/warpboard/linux-4.0.config"
>>
>>  You forgot to include this file in the patch. Please make sure that it's a
>> defconfig, not a full config.
>>
> 
> This file is present later in a different email.
> git send email command send a mail per commit. Do I use the good process to provide my patch ? Do you prefer to put all the patch in the same email ?

 Yes, you should use 'git rebase -i origin/master' to rebase your changes on top
of the buildroot master, and then squash everything into a single commit. For
this case, I don't see a reason to split it into separate commits.

 Remember to add a changelog to the commit message, like so:

...
Signed-off-by: ...
---
Changes v2: ....


[snip]

>>  We also usually add a readme.txt file with an explanation of how to put
>> everything on an SD card.
>>
> 
> There is no sdcard port available on warpboard. The only way to flash it is to used dfu/imx_usb_loader.
> But you right, I will add in a README a process to flash the board.

 In that case, it's definitely important to have a readme file. And you probably
also want to add BR2_PACKAGE_HOST_IMX_USB_LOADER=y to the defconfig.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2015-06-21 13:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 15:29 [Buildroot] [PATCH 1/4] defconfig for warpboard Arthur LAMBERT
2015-06-19 15:29 ` [Buildroot] [PATCH 2/4] README file for wifi/bluetooth support Arthur LAMBERT
2015-06-19 15:29 ` [Buildroot] [PATCH 3/4] fix bluetooth support on kernel 4.0, and warpboard kernel config Arthur LAMBERT
2015-06-19 15:29 ` [Buildroot] [PATCH 4/4] firmware file for wifi Arthur LAMBERT
2015-06-19 17:20   ` Yann E. MORIN
2015-06-21  0:49     ` Arthur LAMBERT
2015-06-21 10:16       ` Yann E. MORIN
2015-06-19 21:48 ` [Buildroot] [PATCH 1/4] defconfig for warpboard Arnout Vandecappelle
2015-06-19 22:00   ` Arnout Vandecappelle
2015-06-21  1:00     ` Arthur LAMBERT
2015-06-21 13:26       ` Arnout Vandecappelle
2015-06-20  9:44   ` Arnout Vandecappelle
2015-06-21  0:56   ` Arthur LAMBERT
2015-06-21 13:32     ` Arnout Vandecappelle [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=5586BCF4.4070405@mind.be \
    --to=arnout@mind.be \
    --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