mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Frank Scheiner <frank.scheiner@web.de>
Cc: akpm@linux-foundation.org, allen.lkml@gmail.com,
	broonie@kernel.org, conor@kernel.org, f.fainelli@gmail.com,
	gregkh@linuxfoundation.org, jonathanh@nvidia.com,
	linux-kernel@vger.kernel.org, linux@roeck-us.net,
	lkft-triage@lists.linaro.org, patches@kernelci.org,
	patches@lists.linux.dev, pavel@denx.de, rwarsow@gmx.de,
	shuah@kernel.org, srw@sladewatkins.net, stable@vger.kernel.org,
	sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 6.1 000/440] 6.1.103-rc1 review
Date: Tue, 30 Jul 2024 17:52:26 -0600	[thread overview]
Message-ID: <29aa906b-a026-46ca-83a9-43d0e8d6e779@linuxfoundation.org> (raw)
In-Reply-To: <017486e3-2132-44a0-ade8-94647de78cef@web.de>

On 7/30/24 17:37, Frank Scheiner wrote:
> Hi,
> 
> could be the same issue as for me, see [1] for details.
> 
> [1]:
> https://lore.kernel.org/stable/de6f52bb-c670-4e03-9ce1-b4ee9b981686@web.de/
> 
> Does applying 6259151c04d4e0085e00d2dcb471ebdd1778e72e from mainline
> (adapt hunk #2 to cleanly apply) help in your case, too, or do you maybe
> detected a different issue?
> 

Thank you for the tip. I will try this first to see if this fixes the problem
for me.

thanks,
-- Shuah


  reply	other threads:[~2024-07-30 23:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 15:43 Greg Kroah-Hartman
2024-07-30 22:40 ` Florian Fainelli
2024-07-30 23:18 ` Shuah Khan
2024-07-30 23:37   ` Frank Scheiner
2024-07-30 23:52     ` Shuah Khan [this message]
2024-07-30 23:24 ` Frank Scheiner
2024-07-31  6:07   ` Greg KH
2024-07-31  9:24 ` Naresh Kamboju
2024-07-31 16:13   ` Jens Axboe
2024-07-31 16:46     ` Dan Carpenter
2024-07-31 16:49       ` Jens Axboe
2024-07-31 14:42 ` Peter Schneider
2024-08-01  8:28 ` Shreeya Patel

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=29aa906b-a026-46ca-83a9-43d0e8d6e779@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=frank.scheiner@web.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®