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>,
Michael Schmitz <schmitzmic@gmail.com>
Subject: Re: Status of affs support in the kernel and affstools
Date: Tue, 20 Jun 2023 23:27:00 +0200 [thread overview]
Message-ID: <4858709.31r3eYUQgx@lichtvoll.de> (raw)
In-Reply-To: <25787bdeb7560871ebb8678a3f09f62eed418dc4.camel@physik.fu-berlin.de>
Hi John, hi Artem, hi Michael.
John Paul Adrian Glaubitz - 13.06.23, 09:22:52 CEST:
> On Tue, 2023-06-13 at 09:20 +0200, Martin Steigerwald wrote:
> > 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.
> >
> > (...)
> > 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.
>
> I greatly appreciate that. Thanks a lot for taking care of this!
The Amiga RDB large partition fixes went in now.
Thanks to everyone involved! Special thanks to Michael for going through
13 iterations!
https://lore.kernel.org/linux-m68k/10e23e7d-d2b0-f540-f0aa-ca83727fa10e@gmail.com/T/#m0eea1b4b33ff8d96ebfe35546bce3a67256ee166
---------- Weitergeleitete Nachricht ----------
Betreff: Re: [PATCH v13 0/3] Amiga RDB partition support fixes
Datum: Dienstag, 20. Juni 2023, 22:28:34 CEST
Von: Jens Axboe <axboe@kernel.dk>
An: linux-block@vger.kernel.org, Michael Schmitz <schmitzmic@gmail.com>
Kopie: linux-m68k@vger.kernel.org, geert@linux-m68k.org, hch@lst.de,
martin@lichtvoll.de, fthain@linux-m68k.org
On Wed, 21 Jun 2023 08:17:22 +1200, Michael Schmitz wrote:
> another last version of this patch series, only change
> in this version is in the patch 2 subject (to better
> reflect what it's about), and adding Geert's review
> tag to said patch.
>
> I hope I've crossed all i's and dotted all t's now...
>
> [...]
Applied, thanks!
[1/3] block: fix signed int overflow in Amiga partition support
commit: fc3d092c6bb48d5865fec15ed5b333c12f36288c
[2/3] block: change all __u32 annotations to __be32 in affs_hardblocks.h
commit: 95a55437dc49fb3342c82e61f5472a71c63d9ed0
[3/3] block: add overflow checks for Amiga partition support
commit: b6f3f28f604ba3de4724ad82bea6adb1300c0b5f
Best regards,
--
Jens Axboe
-------------------------------------------------------------
Thanks,
--
Martin
next prev parent reply other threads:[~2023-06-20 21:27 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
2023-06-13 7:22 ` John Paul Adrian Glaubitz
2023-06-20 21:27 ` Martin Steigerwald [this message]
[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=4858709.31r3eYUQgx@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 \
--cc=schmitzmic@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