public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Martin Steigerwald <martin@lichtvoll.de>,
	Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org
Cc: linux-m68k@vger.kernel.org, geert@linux-m68k.org,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v7 2/2] block: add overflow checks for Amiga partition support
Date: Tue, 13 Jun 2023 20:18:24 +1200	[thread overview]
Message-ID: <12241273-9403-426e-58ed-f3f597fe331b@gmail.com> (raw)
In-Reply-To: <4814181.GXAFRqVoOG@lichtvoll.de>

Hi Martin,

Am 13.06.2023 um 19:25 schrieb Martin Steigerwald:
> Hi Michael, hi Jens, Hi Geert.
>
> Michael Schmitz - 22.08.22, 22:56:10 CEST:
>> On 23/08/22 08:41, Jens Axboe wrote:
>>> On 8/22/22 2:39 PM, Michael Schmitz wrote:
>>>> Hi Jens,
>>>>
>>>> will do - just waiting to hear back what needs to be done regarding
>>>> backporting issues raised by Geert.
>>>
>>> It needs to go upstream first before it can go to stable. Just mark
>>> it with the right Fixes tags and that will happen automatically.
> […]
>> thanks - the Fixes tag in my patches refers to Martin's bug report and
>> won't be useful to decide how far back this must be applied.
>>
>> Now the bug pre-dates git, making the commit to 'fix'
>> 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 ... That one's a bit special,
>> please yell if you want me to lie about this and use a later commit
>> specific to the partition parser code.
>
> After this discussion happened I thought the patch went in. However… as
> John Paul Adrian asked in "Status of affs support in the kernel and
> affstools" thread on linux-m68k and debian-68k mailing list, I searched
> for the patch in git history but did not find it.

I may have messed that one up, as it turns out. Last version was v9 
which I had to resend twice, and depending on what Jens uses to keep 
track of patches, the resends may not have shown up in his tool. I 
should have bumped the version number instead.

I'll see if my latest version still applies cleanly ...

Cheers,

	Michael


> So did it go in meanwhile?
>
> Ciao,
>

  reply	other threads:[~2023-06-13  8:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1539570747-19906-1-git-send-email-schmitzmic@gmail.com>
     [not found] ` <1539570747-19906-3-git-send-email-schmitzmic@gmail.com>
2022-07-25 12:36   ` [PATCH v7 2/2] block: add overflow checks for Amiga partition support Martin Steigerwald
2022-07-25 23:03     ` Jens Axboe
2022-07-26  1:53       ` Michael Schmitz
2022-07-26  3:40         ` Jens Axboe
2022-07-26  3:58           ` Michael Schmitz
2022-08-21 20:59             ` Martin Steigerwald
2022-08-22  5:46               ` Michael Schmitz
2022-08-22 13:57                 ` Jens Axboe
2022-08-22 20:39                   ` Michael Schmitz
2022-08-22 20:41                     ` Jens Axboe
2022-08-22 20:56                       ` Michael Schmitz
2023-06-13  7:25                         ` Martin Steigerwald
2023-06-13  8:18                           ` Michael Schmitz [this message]
2023-06-13 10:57                             ` Martin Steigerwald
2023-06-13 22:11                               ` Michael Schmitz
2023-06-14  0:07                                 ` Finn Thain
2023-06-14  1:20                                   ` Michael Schmitz
2023-06-14  7:19                                 ` Martin Steigerwald
2023-06-14  8:43                                   ` Michael Schmitz
     [not found]                                     ` <05bd2c1b-a985-d935-a955-06a048d54c18@earthlink.net>
2023-06-14 19:46                                       ` Michael Schmitz
2023-06-15  0:13                                     ` Finn Thain
2023-06-15  1:06                                       ` Michael Schmitz
2023-06-15  4:28                                       ` Christoph Hellwig

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=12241273-9403-426e-58ed-f3f597fe331b@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=geert@linux-m68k.org \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=martin@lichtvoll.de \
    /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