From: Michael Schmitz <schmitzmic@gmail.com>
To: "Ingo Jürgensmann" <ij@2014.bluespice.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Debian m68k <debian-68k@lists.debian.org>
Subject: Re: m68k v3.16 status update
Date: Fri, 08 Aug 2014 20:58:56 +1200 [thread overview]
Message-ID: <53E49150.60307@gmail.com> (raw)
In-Reply-To: <06A072CC-7C42-47C2-A877-9012C3DE6585@2014.bluespice.org>
Hi Ingo,
> Am 05.08.2014 um 21:40 schrieb Geert Uytterhoeven <geert@linux-m68k.org>:
>
>
>> m68k v3.16 is out!
>> git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
>> m68k-queue is getting smaller, but there are still a few commits left:
>>
>
> Hmm, what about the Blizzard 2060 SCSI driver from Michael & Tuomas? It runs since then on Akire...
>
So it still runs OK - good to know.
I understand Geert's reply to Adrian to please take this patch through
the SCSI maintainer, not m68k. Fair enough. We'll leave it as 2060 only
driver for now and add other boards later.
Cheers,
Michael
next prev parent reply other threads:[~2014-08-08 8:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 19:40 m68k v3.16 status update Geert Uytterhoeven
2014-08-05 19:52 ` Ingo Jürgensmann
2014-08-05 20:29 ` John Paul Adrian Glaubitz
2014-08-06 7:35 ` Geert Uytterhoeven
2014-08-06 9:53 ` John Paul Adrian Glaubitz
2014-08-08 8:58 ` Michael Schmitz [this message]
2014-08-08 9:53 ` Tuomas Vainikka
2014-08-08 8:38 ` Michael Schmitz
2014-08-08 9:45 ` Christian T. Steigies
2014-08-08 22:33 ` Michael Schmitz
2014-08-08 14:25 ` Tuomas Vainikka
2014-08-08 22:25 ` Michael Schmitz
2014-08-09 6:45 ` Tuomas Vainikka
2014-08-10 1:44 ` Michael Schmitz
2017-12-14 4:47 ` Michael Schmitz
2017-12-14 12:07 ` Vainikka Tuomas
2017-12-14 13:20 ` John Paul Adrian Glaubitz
2017-12-14 18:40 ` Michael Schmitz
2017-12-14 23:49 ` Finn Thain
2017-12-19 0:40 ` Michael Schmitz
2017-12-19 3:35 ` Finn Thain
2017-12-19 6:11 ` Michael Schmitz
2017-12-19 22:06 ` zorro_esp, was " Finn Thain
2017-12-19 23:01 ` Finn Thain
2017-12-20 1:42 ` Michael Schmitz
2017-12-20 3:34 ` Finn Thain
2017-12-28 8:02 ` Michael Schmitz
2017-12-29 0:02 ` Finn Thain
2017-12-29 9:09 ` Michael Schmitz
2017-12-19 8:19 ` Geert Uytterhoeven
2017-12-20 7:33 ` zorro_esp, was: " Michael Schmitz
2017-12-20 8:13 ` Geert Uytterhoeven
2017-12-15 8:34 ` Vainikka Tuomas
2017-12-16 0:04 ` TCQ with zorro_esp, was " Finn Thain
2017-12-19 0:44 ` Michael Schmitz
2014-08-09 1:14 ` Michael Schmitz
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=53E49150.60307@gmail.com \
--to=schmitzmic@gmail.com \
--cc=debian-68k@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=ij@2014.bluespice.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).