From: Borislav Petkov <bp@alien8.de>
To: Sami Tolvanen <samitolvanen@google.com>
Cc: Luca Stefani <luca.stefani.ge1@gmail.com>,
Tony Luck <tony.luck@intel.com>,
linux-edac@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] RAS/CEC: Fix cec_init prototype
Date: Mon, 17 Aug 2020 20:54:36 +0200 [thread overview]
Message-ID: <20200817185436.GO549@zn.tnic> (raw)
In-Reply-To: <CABCJKud6M+u-TUZ2w5zdPPnwJQ1b7wxXwg8Rnoc=rBC6zMvRxA@mail.gmail.com>
On Mon, Aug 17, 2020 at 11:11:02AM -0700, Sami Tolvanen wrote:
> Not the toolchain, the tree has patches for LTO+CFI, which tends to
> break with type mismatches. This doesn't affect just building the
> kernel with Clang without other changes.
Ok, that explains it.
As for why I'm still chasing down the exact reason for the reported
breakage: this will determine the urgency with which this fix is handled
and to which trees it needs to go so please be more precise next time
when saying "it broke". :)
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-08-17 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 16:18 [PATCH] RAS/CEC: Fix cec_init prototype Luca Stefani
2020-08-05 4:59 ` Borislav Petkov
2020-08-05 9:57 ` [PATCH v2] " Luca Stefani
2020-08-12 21:09 ` Sami Tolvanen
2020-08-17 15:13 ` Borislav Petkov
2020-08-17 15:58 ` Sami Tolvanen
2020-08-17 17:41 ` Borislav Petkov
2020-08-17 18:11 ` Sami Tolvanen
2020-08-17 18:54 ` Borislav Petkov [this message]
2020-08-18 9:02 ` [tip: ras/core] RAS/CEC: Fix cec_init() prototype tip-bot2 for Luca Stefani
2020-08-20 8:36 ` tip-bot2 for Luca Stefani
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=20200817185436.GO549@zn.tnic \
--to=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.stefani.ge1@gmail.com \
--cc=samitolvanen@google.com \
--cc=tony.luck@intel.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.