All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: Sasha Levin <sashal@kernel.org>,
	Georgi Djakov <djakov@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Stable <stable@vger.kernel.org>,
	Yongqin Liu <yongqin.liu@linaro.org>
Subject: Re: [PATCH for-6.1.y] Revert "interconnect: qcom: sm8250: Enable sync_state"
Date: Mon, 8 Jan 2024 16:19:14 +0100	[thread overview]
Message-ID: <2024010845-widget-ether-ccd9@gregkh> (raw)
In-Reply-To: <CAMi1Hd37L6NYKNpGOUnT7EO8kfc-HVQUqnoTTARA5gTpTc2wXQ@mail.gmail.com>

On Mon, Jan 08, 2024 at 08:33:00PM +0530, Amit Pundir wrote:
> On Mon, 8 Jan 2024 at 19:42, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Sun, Jan 07, 2024 at 09:27:02PM +0530, Amit Pundir wrote:
> > > This reverts commit 3637f6bdfe2ccd53c493836b6e43c9a73e4513b3 which is
> > > commit bfc7db1cb94ad664546d70212699f8cc6c539e8c upstream.
> > >
> > > This resulted in boot regression on RB5 (sm8250), causing the device
> > > to hard crash into USB crash dump mode everytime.
> > >
> > > Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
> >
> > Any link to that report?  Is this also an issue in 6.7 and/or 6.6.y?
> 
> Here is a fresh RB5 crash report running AOSP with upstream v6.1.71
> https://lkft.validation.linaro.org/scheduler/job/7151629#L4239
> 
> I do not see this crash on v6.7.

So does that mean we are instead missing something here for this tree?

thanks,

greg k-h

  reply	other threads:[~2024-01-08 15:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07 15:57 [PATCH for-6.1.y] Revert "interconnect: qcom: sm8250: Enable sync_state" Amit Pundir
2024-01-08 14:12 ` Greg KH
2024-01-08 15:03   ` Amit Pundir
2024-01-08 15:19     ` Greg KH [this message]
2024-01-08 15:30       ` Konrad Dybcio
2024-01-08 15:34         ` Greg KH

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=2024010845-widget-ether-ccd9@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=amit.pundir@linaro.org \
    --cc=djakov@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yongqin.liu@linaro.org \
    /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.