mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jakov Novak" <jakovnovak30@gmail.com>
To: "Johan Hovold" <johan@kernel.org>,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Ulf Hansson" <ulfh@kernel.org>,
	"Jakov Novak" <jakovnovak30@gmail.com>,
	<linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-kernel-mentees@lists.linux.dev>,
	"Guangshuo Li" <lgs201920130244@gmail.com>,
	"Runyu Xiao" <runyu.xiao@seu.edu.cn>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	<syzbot+1ee4f3b9228e35f14677@syzkaller.appspotmail.com>
Subject: Re: [PATCH] mmc: vub300: fix sleeping function call from invalid context in vub300_inactivity_timer_expired
Date: Fri, 11 Sep 2026 13:14:20 +0200	[thread overview]
Message-ID: <DLCFZ1Z5FV92.3JAXNVQWJZGN8@gmail.com> (raw)
In-Reply-To: <aqOoBwBav8JZhMQ9@hovoldconsulting.com>

Hi Johan,

> Thanks for taking a look. I guess we should fix this inconsistency in
> MMC core eventually, but that the vub300 needs to be reworked to handle
> this quirk in the mean time.

Should I send a v2 based on my first patch with the Reported-by,
Tested-by and Fixes tags fixed or is there something else I missed? 

Best,
Jakov

      reply	other threads:[~2026-09-11 11:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-16 15:38 Jakov Novak
2026-08-17  8:13 ` Johan Hovold
2026-08-30  9:32   ` Tetsuo Handa
2026-09-07 11:16     ` Jakov Novak
2026-09-07 12:19       ` Geert Uytterhoeven
2026-09-07 12:17   ` Geert Uytterhoeven
2026-09-07 13:55     ` Johan Hovold
2026-09-07 14:48       ` Geert Uytterhoeven
2026-09-09  6:57         ` Johan Hovold
2026-09-09  7:38           ` Geert Uytterhoeven
2026-09-09  8:02             ` Johan Hovold
2026-09-09 17:24           ` Wolfram Sang
2026-09-11  7:04             ` Johan Hovold
2026-09-11 11:14               ` Jakov Novak [this message]

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=DLCFZ1Z5FV92.3JAXNVQWJZGN8@gmail.com \
    --to=jakovnovak30@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=johan@kernel.org \
    --cc=lgs201920130244@gmail.com \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=runyu.xiao@seu.edu.cn \
    --cc=skhan@linuxfoundation.org \
    --cc=syzbot+1ee4f3b9228e35f14677@syzkaller.appspotmail.com \
    --cc=ulfh@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

all inboxes | Powered by JetHome®