public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
	Debian m68k <debian-68k@lists.debian.org>
Subject: Re: [PATCH 0/4] Atari kernel-in-FastRAM patches, take three
Date: Mon, 31 Mar 2014 20:54:38 +1300	[thread overview]
Message-ID: <53391F3E.1090005@gmail.com> (raw)
In-Reply-To: <CAMuHMdV_6e0qsrP6H6mguJ53inndFR--0MYG9KM9iso=F3X0Rg@mail.gmail.com>

Hi Geert,


> Hi Michael,
>
> On Sun, Mar 30, 2014 at 1:01 AM, Michael Schmitz <schmitzmic@gmail.com> wrote:
>> see the following patch series for the hopefully final word on
>> the 'make ST-RAM pool accessible for kernels running from FastRAM'
>> story.
> When submitting a "take three", please annotate the individual patches
> with "[PATCH v3 x/y]".

Will follow shortly.

> It would also have been nice to CC the block resp. SCSI maintainers to
> get their acks for patches 3 and 4, but I'm gonna take them through the
> m68k tree anyway.

I'll do that anyway - not that I've got much hope to elicit a response 
from either. Still waiting for feedback from the last SCSI patches sent 
there.

(Not that I'm any better - still haven't given Finn's patches a try...)

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

      reply	other threads:[~2014-03-31  7:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-30  0:01 [PATCH 0/4] Atari kernel-in-FastRAM patches, take three Michael Schmitz
2014-03-30  0:01 ` [PATCH 1/4] m68k/atari - stram: alloc ST-RAM pool even if kernel not in ST-RAM Michael Schmitz
2014-03-30 19:11   ` Geert Uytterhoeven
2014-03-31  1:58     ` Michael Schmitz
2014-03-30  0:01 ` [PATCH 2/4] m68k/atari - atafb: convert allocation of fb ram to new interface Michael Schmitz
2014-03-30 19:11   ` Geert Uytterhoeven
2014-03-30  0:01 ` [PATCH 3/4] m68k/atari - ataflop: use correct virt/phys translation for DMA buffer Michael Schmitz
2014-03-31  7:46   ` Geert Uytterhoeven
2014-03-31 14:28     ` Jens Axboe
2014-03-30  0:01 ` [PATCH 4/4] m68k/atari - atari_scsi: " Michael Schmitz
2014-03-31  7:48   ` Geert Uytterhoeven
2014-03-30 22:34 ` [PATCH 0/4] Atari kernel-in-FastRAM patches, take three Andreas Schwab
2014-03-31  1:55   ` Michael Schmitz
2014-03-31 20:58     ` Andreas Schwab
2014-03-31 21:24       ` Michael Schmitz
2014-03-31 22:39         ` Andreas Schwab
2014-03-31 23:52           ` Michael Schmitz
2014-04-01  7:28             ` Geert Uytterhoeven
2014-04-01  7:45               ` schmitz
2014-04-01  7:50                 ` Geert Uytterhoeven
2014-04-01 12:23               ` Finn Thain
2014-04-01 12:41                 ` Geert Uytterhoeven
2014-04-01 18:56                 ` Michael Schmitz
2014-04-04  6:12                   ` Finn Thain
2014-04-09  6:44                     ` Finn Thain
2014-04-04  3:43                 ` Scott Holder
2014-04-04  6:08                   ` Finn Thain
2014-04-01  7:24         ` Geert Uytterhoeven
2014-04-01  7:39           ` schmitz
2014-04-01  7:49             ` Geert Uytterhoeven
2014-04-01  8:12               ` schmitz
2014-04-01  8:23                 ` Geert Uytterhoeven
2014-04-01  9:06             ` Andreas Schwab
2014-03-31  7:42 ` Geert Uytterhoeven
2014-03-31  7:54   ` 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=53391F3E.1090005@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=debian-68k@lists.debian.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.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