All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: debian-68k <debian-68k@lists.debian.org>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: linux-m68k <linux-m68k@lists.linux-m68k.org>,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: Status of affs support in the kernel and affstools
Date: Tue, 13 Jun 2023 09:20:29 +0200	[thread overview]
Message-ID: <5947812.lOV4Wx5bFT@lichtvoll.de> (raw)
In-Reply-To: <baa520109ab3a13d1ac8aca1c9b8eaeee070c241.camel@physik.fu-berlin.de>

John Paul Adrian Glaubitz - 13.06.23, 08:47:11 CEST:
> I was wondering what the current status of the affs driver in the
> kernel is, did it receive the fixes that Michael(?) was working on? I
> vaguely remember there were some issues with larger filesystems or so
> and that someone was working on fixing these issues.

Well I just searched for the large size fixing patches discussed on 
linux-m68k mailing list under subject titles "Amiga RDB partition 
support fixes":

While I found a steady stream of fixes for affs, including related to 
Amiga permission bit handling, quite recent fixes, even in 2023, I did 
not found that size fixing patch.

I recalled a discussion where Michael Schmitz talked to Jens Axboe after 
I asked whether the patch got in on 2023-08-21. I thought back then it 
would have went in, but maybe the last question asked by Jens Axboe did 
not get answered?

At least I did not found the patch in git history. Maybe I made a 
mistake during search.

I will reply to the other thread and ask again. Maybe it was just a last 
question / answer round missing. Or maybe someone else can confirm that 
the patch indeed went in.

Best,
-- 
Martin



  parent reply	other threads:[~2023-06-13  7:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13  6:47 Status of affs support in the kernel and affstools John Paul Adrian Glaubitz
2023-06-13  6:53 ` Artem Bityutskiy
2023-06-13  7:05   ` John Paul Adrian Glaubitz
2023-06-13  7:20 ` Martin Steigerwald [this message]
2023-06-13  7:22   ` John Paul Adrian Glaubitz
2023-06-20 21:27     ` Martin Steigerwald
     [not found] ` <CABq5eXGMA=5U_h3ZbfXt_weZNWh5zviFn3rw9oxS=wFc6d1Vsw@mail.gmail.com>
2023-06-13  7:21   ` John Paul Adrian Glaubitz

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=5947812.lOV4Wx5bFT@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=debian-68k@lists.debian.org \
    --cc=dedekind1@gmail.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@lists.linux-m68k.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.