Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Sergio Callegari <sergio.callegari@gmail.com>,
	linux-scsi@vger.kernel.org
Subject: Re: Sd card race on resume with filesystem errors (possible data loss?)
Date: Fri, 9 Jan 2026 12:57:44 -0800	[thread overview]
Message-ID: <fe070d43-f9b2-45b2-95d8-477154b28dea@acm.org> (raw)
In-Reply-To: <3bb03946-eb11-4e28-a72b-e958833bb5cc@gmail.com>

On 1/2/26 2:15 AM, Sergio Callegari wrote:
> 5. Purism developers have a kernel patch for it at https:// 
> source.puri.sm/Librem5/linux/-/merge_requests/788. From my understandig, 
> this is not in linux mainline or stable. Would it make sense to consider 
> that patch?

Please post the patch on the linux-scsi mailing list if you want it
included in the upstream kernel.

Thanks,

Bart.

  reply	other threads:[~2026-01-09 20:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02  9:15 Sd card race on resume with filesystem errors (possible data loss?) Sergio Callegari
2026-01-09 20:57 ` Bart Van Assche [this message]
2026-01-20 12:19   ` Sergio Callegari
2026-01-24 20:38     ` Sergio Callegari

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=fe070d43-f9b2-45b2-95d8-477154b28dea@acm.org \
    --to=bvanassche@acm.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sergio.callegari@gmail.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