From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
Huacai Chen <chenhuacai@loongson.cn>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Collabora Kernel ML <kernel@collabora.com>
Subject: Re: [PATCH 2/3] MIPS: Only fiddle with CHECKFLAGS if `need-compiler'
Date: Tue, 18 Jul 2023 16:45:36 +0200 [thread overview]
Message-ID: <83ac823f-eca4-9dda-c692-55b7a16bcc1e@collabora.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2307181421010.61566@angie.orcam.me.uk>
Please also mention the KernelCI bot as this was initially found
thanks to an automated email report:
On 18/07/2023 16:37, Maciej W. Rozycki wrote:
> Reported-by: Guillaume Tucker <guillaume.tucker@collabora.com>
Reported-by: "kernelci.org bot" <bot@kernelci.org>
Thanks,
Guillaume
next prev parent reply other threads:[~2023-07-18 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 14:37 [PATCH 0/3] MIPS: Fix build issues from the introduction of `need-compiler' Maciej W. Rozycki
2023-07-18 14:37 ` [PATCH 1/3] MIPS: Fix CONFIG_CPU_DADDI_WORKAROUNDS `modules_install' regression Maciej W. Rozycki
2023-07-19 11:34 ` Philippe Mathieu-Daudé
2023-07-18 14:37 ` [PATCH 2/3] MIPS: Only fiddle with CHECKFLAGS if `need-compiler' Maciej W. Rozycki
2023-07-18 14:45 ` Guillaume Tucker [this message]
2023-07-18 14:37 ` [PATCH 3/3] Revert MIPS: Loongson: Fix build error when make modules_install Maciej W. Rozycki
2023-07-18 14:54 ` [PATCH 0/3] MIPS: Fix build issues from the introduction of `need-compiler' Huacai Chen
2023-07-19 15:39 ` Maciej W. Rozycki
2023-07-20 1:55 ` Huacai Chen
2023-07-21 10:53 ` Maciej W. Rozycki
2023-07-25 8:44 ` Thomas Bogendoerfer
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=83ac823f-eca4-9dda-c692-55b7a16bcc1e@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=chenhuacai@loongson.cn \
--cc=jbglaw@lug-owl.de \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for NNTP newsgroup(s).