From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Philip-Dylan Gleonec <philip-dylan@gleonec.bzh>
Cc: Fabio Estevam <festevam@gmail.com>,
kilian.zinnecker@mail.de, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 0/2] Udoo Neo kernel update
Date: Thu, 1 Aug 2024 23:20:14 +0200 [thread overview]
Message-ID: <20240801232014.6ec310ce@windsurf> (raw)
In-Reply-To: <20240801153432.1741409-1-philip-dylan@gleonec.bzh>
On Thu, 1 Aug 2024 17:34:30 +0200
Philip-Dylan Gleonec <philip-dylan@gleonec.bzh> wrote:
> Philip-Dylan Gleonec (2):
> configs/mx6sx_udoo_neo_defconfig: bump kernel to 6.6.43
> configs/mx6sx_udoo_neo_defconfig: add hashes
Thanks, both patches applied! A couple of small comments to improve
your future contributions:
- In the first patch, I added a short extract of the kernel build error
being fixed, and also a link to the Gitlab CI failure being fixed by
this. See the final commit
at https://gitlab.com/buildroot.org/buildroot/-/commit/44b921f605dffd07bb6294e6368c2ace34a08266
- In the commit title, we normally use "configs/foo:" instead of
"configs/foo_defconfig:". No strong reason, just a habit, and we like
to be consistent.
- The wrapping/paragraph organization of your commit messages was a bit
strange and not really consistent with what is done in Buildroot, but
also in the kernel. Basically you tend to do:
Some explanation here.
Then some more explanation that might
span multiple
lines.
Then another explanations.
While in most projects, including Buildroot, we expect:
Some explanation here.
Then some more explanation that might span
multiple lines.
Then another paragraph about something else.
- If you do have this board, it would be nice to add yourself for this
defconfig, and its data file in board/ in the DEVELOPERS file. This
way you will receive notifications when the build of this defconfig
is broken, or when someone submits a patch touching this defconfig.
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-01 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 14:55 [Buildroot] [PATCH 0/2] Udoo Neo kernel update Philip-Dylan Gleonec
2024-07-31 14:55 ` [Buildroot] [PATCH 1/2] configs/mx6sx_udoo_neo_defconfig: bump kernel to 6.6.43 Philip-Dylan Gleonec
2024-07-31 14:55 ` [Buildroot] [PATCH 2/2] configs/mx6sx_udoo_neo_defconfig: add hashes Philip-Dylan Gleonec
2024-07-31 17:01 ` Fabio Estevam
2024-07-31 19:51 ` Philip-Dylan Gleonec
2024-07-31 19:57 ` Fabio Estevam
2024-08-01 15:34 ` [Buildroot] [PATCH v2 0/2] Udoo Neo kernel update Philip-Dylan Gleonec
2024-08-01 15:34 ` [Buildroot] [PATCH v2 1/2] configs/mx6sx_udoo_neo_defconfig: bump kernel to 6.6.43 Philip-Dylan Gleonec
2024-08-01 15:34 ` [Buildroot] [PATCH v2 2/2] configs/mx6sx_udoo_neo_defconfig: add hashes Philip-Dylan Gleonec
2024-08-01 21:20 ` Thomas Petazzoni via buildroot [this message]
2024-08-03 17:15 ` [Buildroot] [PATCH v2 0/2] Udoo Neo kernel update Philip-Dylan Gleonec
-- strict thread matches above, loose matches on Subject: below --
2024-08-01 18:58 kilian.zinnecker--- via buildroot
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=20240801232014.6ec310ce@windsurf \
--to=buildroot@buildroot.org \
--cc=festevam@gmail.com \
--cc=kilian.zinnecker@mail.de \
--cc=philip-dylan@gleonec.bzh \
--cc=thomas.petazzoni@bootlin.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 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.