From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "Simek, Michal" <michal.simek@amd.com>,
"Erkiaga Elorza, Ibai" <ibai.erkiaga-elorza@amd.com>,
"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
Neal Frager via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v8 01/10] package/binutils-bare-metal: new package
Date: Thu, 14 Dec 2023 08:48:06 +0100 [thread overview]
Message-ID: <20231214084806.329afc53@windsurf> (raw)
In-Reply-To: <CH2PR12MB5004A76EDFB561312927A1D4F08CA@CH2PR12MB5004.namprd12.prod.outlook.com>
On Thu, 14 Dec 2023 07:10:39 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> I just made a patch which removes my post install fixup with the
> newlib configure script patch.
>
> Below you can find a pull request to apply it to your bare-metal
> branch: https://github.com/tpetazzoni/buildroot/pull/1
As replied to another e-mail, the newlib patch will have to be improved
to make tooldir configurable, as I don't think your patch can be
acceptable as-is in newlib, as it would break things for existing users.
Also, the way your formatted the patch is not correct: you have made
yourself the author of the patch, but you kept the original author of
the patch as the first Signed-off-by. Golden rule: the patch author
must *always* match the first Signed-off-by line.
So here two options:
- You want to keep the original author: he must appear as From: and
first Signed-off-by, you add your Signed-off-by after, to indicate
that you're conveying the patch
- You want to make yourself the author because you made substantial
changes: you must appear as From: and first Signed-off-by, and then
you can put a Co-Developed-By: or something like that to credit the
original author.
Best regards,
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:[~2023-12-14 7:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 7:34 [Buildroot] [PATCH v8 01/10] package/binutils-bare-metal: new package Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 02/10] package/gcc-bare-metal: " Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 03/10] package/newlib-bare-metal: " Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 04/10] toolchain/toolchain-bare-metal-buildroot: new toolchain Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 05/10] boot/zynqmp-firmware: new boot firmware Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 06/10] boot/uboot.mk: new zynqmp pmufw build option Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 07/10] configs/zynqmp*: build pmufw source Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 08/10] boot/versal-firmware: new boot firmware Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 09/10] configs/versal_vck190_defconfig: build plm and psmfw source Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 10/10] package/versal-firmware: remove package Neal Frager via buildroot
2023-12-13 22:28 ` [Buildroot] [PATCH v8 01/10] package/binutils-bare-metal: new package Thomas Petazzoni via buildroot
2023-12-14 5:29 ` Frager, Neal via buildroot
2023-12-14 7:41 ` Thomas Petazzoni via buildroot
2023-12-14 7:51 ` Frager, Neal via buildroot
2023-12-14 7:58 ` Thomas Petazzoni via buildroot
2023-12-14 8:12 ` Frager, Neal via buildroot
2023-12-14 9:15 ` Thomas Petazzoni via buildroot
2023-12-14 14:43 ` Frager, Neal via buildroot
2023-12-15 9:40 ` Frager, Neal via buildroot
2023-12-14 7:10 ` Frager, Neal via buildroot
2023-12-14 7:48 ` Thomas Petazzoni via buildroot [this message]
2023-12-14 7:57 ` Frager, Neal via buildroot
2024-01-12 7:20 ` Frager, Neal 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=20231214084806.329afc53@windsurf \
--to=buildroot@buildroot.org \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--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.