Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] i2c: i2c-boardinfo: Annotate code used in init phase only
Date: Sat, 18 Oct 2025 22:08:04 +0200	[thread overview]
Message-ID: <8438d7d5-4f71-4244-a436-b3c747cdb81d@gmail.com> (raw)
In-Reply-To: <dfa9078d-7c08-4fc1-9926-e5996d10a1c2@oss.qualcomm.com>

On 10/11/2025 6:14 PM, Konrad Dybcio wrote:
> On 10/11/25 12:33 PM, Wolfram Sang wrote:
>> Hi Konrad,
>>
>>> Hi, this seems to break booting on Qualcomm X1E80100 Surface Laptop 7
>>> (arm64/boot/dts/qcom/x1e80100-microsoft-romulus.dtsi)
>>>
>>> gcc-14.2 and clang-20.x
>>>
>>> Funnily enough when I build this (albeit on another computer, but also
>>> with clang-20.x) and boot another X1E80100-based device (x1-crd.dtsi
>>> in the same DT dir), it boots up fine
>>
>> I reverted the commit now, but please if you can find out more details
>> about the boot regression, this would be extremly helpful (maybe
>> earlycon helps?).
> 
> I'll try to poke at it the upcoming week, thanks
> 
Any result? It's somewhat unfortunate to revert a change just because of a
vague report w/o evidence / logs / bisect results.

> Konrad


  reply	other threads:[~2025-10-18 20:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8d09aa09-b656-4b69-b01f-3ea40418b7ff@gmail.com>
2025-10-10 19:50 ` [PATCH] i2c: i2c-boardinfo: Annotate code used in init phase only Konrad Dybcio
2025-10-11 10:33   ` Wolfram Sang
2025-10-11 16:14     ` Konrad Dybcio
2025-10-18 20:08       ` Heiner Kallweit [this message]
2025-10-12 21:05   ` Heiner Kallweit

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=8438d7d5-4f71-4244-a436-b3c747cdb81d@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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