From: "J. Neuschäfer via buildroot" <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: "J. Neuschäfer" <j.neuschaefer@gmx.net>,
"J. Neuschäfer via buildroot" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/aer-inject: Fix build error due to missing basename() prototype
Date: Fri, 23 Aug 2024 12:53:22 +0200 [thread overview]
Message-ID: <ZshqIsG6ou9LzJ53@probook> (raw)
In-Reply-To: <20240812214124.2a7b520f@windsurf>
On Mon, Aug 12, 2024 at 09:41:24PM +0200, Thomas Petazzoni wrote:
> Hello J,
Hello Thomas,
> Thanks a lot for your patch, which I have applied. I just have a few
> very, very minor suggestions to further improve your next patches.
>
> First of all, I personally like that the commit title starts with a
> lower-case letter, i.e: "package/aer-inject: fix ..." rather than
> "package/aer-inject: Fix ...".
Ah, force of habit…
>
> On Sun, 11 Aug 2024 12:34:25 +0200
> J. Neuschäfer via buildroot <buildroot@buildroot.org> wrote:
>
> > Fixes several build failures such as:
>
> Please write just "Fixes:". This way, patchwork detects it's a patch
> fixes something, and it flags it as such.
> See https://patchwork.ozlabs.org/project/buildroot/list/, where the column A/F/R/T flags the patches that have a Acked-by:, a Fixes:, a Reviewed-by: or a Tested-by:.
>
> > http://autobuild.buildroot.net/results/e61/e613fc777051be6325d7e3c088d5f723fab518fa/build-end.log
>
> We like to have just:
>
> http://autobuild.buildroot.net/results/e613fc777051be6325d7e3c088d5f723fab518fa/
>
> i.e don't point to build-end.log, but to the build result, and drop the
> extra /e61/ in the URL.
Noted!
> > This patch is from Kuppuswamy Sathyanarayanan's fork of aer-inject. An
> > alternative to including the patch would be to switch to this fork as
> > Buildroot's idea of upstream. Currently, it is the only change in the
> > fork, though.
>
> I guess at this point, it's fine to keep things as they are. How
> "official" is each of those two aer-inject Git repos?
I took a deeper look right now, and found this on the linux-pci mailing list:
https://lore.kernel.org/linux-pci/20240416055035.200085-1-sathyanarayanan.kuppuswamy@linux.intel.com/
Subject: [PATCH v1] PCI/AER: Update aer-inject tool source URL
- https://git.kernel.org/cgit/linux/kernel/git/gong.chen/aer-inject.git/
+ https://github.com/intel/aer-inject.git
This patch was merged, so I think the github.com/intel URL counts as official.
-- jn
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-23 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 10:34 [Buildroot] [PATCH] package/aer-inject: Fix build error due to missing basename() prototype J. Neuschäfer via buildroot
2024-08-12 19:41 ` Thomas Petazzoni via buildroot
2024-08-23 10:53 ` J. Neuschäfer via buildroot [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=ZshqIsG6ou9LzJ53@probook \
--to=buildroot@buildroot.org \
--cc=j.neuschaefer@gmx.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox