From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, Eero Tamminen <oak@helsinkinet.fi>,
Finn Thain <ftain@linux-m68k.org>,
Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH RFC v1] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table
Date: Wed, 1 Mar 2023 08:37:04 +1300 [thread overview]
Message-ID: <d7b2a366-8627-aa57-e4a5-fc9c93bf7b16@gmail.com> (raw)
In-Reply-To: <CAMuHMdW+fsDdOAr=zBuf0k=zO=FEfjFhHsMPbd6inOk=8DFS2g@mail.gmail.com>
Hi Geert,
On 28/02/23 21:08, Geert Uytterhoeven wrote:
> Hi Michael,
>
> On Tue, Feb 28, 2023 at 12:28 AM Michael Schmitz <schmitzmic@gmail.com> wrote:
>> On 28/02/23 09:19, Geert Uytterhoeven wrote:
>>> On Wed, Feb 22, 2023 at 8:52 PM Michael Schmitz <schmitzmic@gmail.com> wrote:
>>>> Link: https://lore.kernel.org/r/daca2f68-19fa-a2b6-97c6-16b5b7e26afe@helsinkinet.fi
>>> 404
>>>
>>> I assume that a message from debian-68k?
>> No, oddly enough that is a message that I have received with CC to
>> linux-m68k (but not from vger!). And mail-archive.com has it:
>>
>> https://www.mail-archive.com/linux-m68k@vger.kernel.org/msg13081.html
>>
>> And also on marc.info:
>>
>> https://marc.info/?l=linux-m68k&m=155477039405576&w=2
> That one has a different Message-ID:
> alpine.LNX.2.21.1904141327340.130@nippy.intranet
I get alpine.LNX.2.21.1904091023540.25@nippy.intranet ...
>
>> Later one with an experimental patch of mine:
>>
>> https://marc.info/?l=linux-m68k&m=155494864731013&w=2
63130691-1984-c423-c1f2-73bfd8d3dcd3@gmail.com
>>
>> None of these messages show up on a search of lore...
> Indeed, and I did receive them through vger.
>
>> What source do you prefer - marc.info or mail-archive.com?
> Let's keep the lore link with the actual Message-ID.
> Missing emails on lore can be backfilled later...
>
> Upon closer look, this predates lore collecting emails, so perhaps
> something went wrong while importing my old archives I sent
> to kernel.org. To be investigated...
OK - I'll send around v2 with lore links and comment removed later.
Cheers,
Michael
>
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
prev parent reply other threads:[~2023-02-28 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 19:50 [PATCH RFC v1] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table Michael Schmitz
2023-02-24 0:31 ` Eero Tamminen
2023-02-24 2:46 ` Michael Schmitz
2023-02-27 20:19 ` Geert Uytterhoeven
2023-02-27 23:28 ` Michael Schmitz
2023-02-28 8:08 ` Geert Uytterhoeven
2023-02-28 19:37 ` Michael Schmitz [this message]
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=d7b2a366-8627-aa57-e4a5-fc9c93bf7b16@gmail.com \
--to=schmitzmic@gmail.com \
--cc=ftain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=oak@helsinkinet.fi \
--cc=schwab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox