From: Phillip Potter <phil@philpotter.co.uk>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Phillip Potter <phil@philpotter.co.uk>,
axboe@kernel.dk, senozhatsky@chromium.org,
linux-block@vger.kernel.org
Subject: Re: [PATCH 0/1] cdrom: patch for inclusion
Date: Wed, 23 Jul 2025 09:02:40 +0100 [thread overview]
Message-ID: <aICXICNEcwutw9C4@equinox> (raw)
In-Reply-To: <eyejjkuzdzl7qlq3os534ckt3jsvvnvp76pyqcrpzcignj3oms@w7cvw6oht5lk>
On Wed, Jul 23, 2025 at 10:14:32AM +0900, Sergey Senozhatsky wrote:
> On (25/07/23 00:18), Phillip Potter wrote:
> > [..] I plan to do more digging regarding this, hopefully
> > this weekend when I have some free time, as I'd really love to replicate
> > the original crash.
>
> I waiting for LG GP65NB60 shipment (arriving today/tomorrow), which
> shows up in crash reports (it should have CDC_MRW_W.) So I'll be able
> to run some tests soon.
Had to fake it with mine by forcing open the relevant code path for the
check to be done. It still didn't crash, so I'll be interested to see
your results. Will hopefully have a dig myself at the weekend :-)
Regards,
Phil
next prev parent reply other threads:[~2025-07-23 8:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 23:18 [PATCH 0/1] cdrom: patch for inclusion Phillip Potter
2025-07-22 23:19 ` [PATCH 1/1] cdrom: Call cdrom_mrw_exit from cdrom_release function Phillip Potter
2025-07-24 3:55 ` Sergey Senozhatsky
2025-07-23 1:10 ` [PATCH 0/1] cdrom: patch for inclusion Jens Axboe
2025-07-23 1:14 ` Sergey Senozhatsky
2025-07-23 8:02 ` Phillip Potter [this message]
2025-07-24 3:54 ` Sergey Senozhatsky
2025-07-24 7:51 ` Sergey Senozhatsky
2025-07-25 7:40 ` Phillip Potter
2025-07-25 7:47 ` Sergey Senozhatsky
-- strict thread matches above, loose matches on Subject: below --
2025-05-14 22:33 Phillip Potter
2024-06-01 22:18 Phillip Potter
2023-10-02 22:02 Phillip Potter
2023-10-03 2:05 ` Jens Axboe
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=aICXICNEcwutw9C4@equinox \
--to=phil@philpotter.co.uk \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=senozhatsky@chromium.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