linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: "Ingo Jürgensmann" <ij@2014.bluespice.org>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>,
	"Debian m68k" <debian-68k@lists.debian.org>,
	karcher@physik.fu-berlin.de
Subject: Re: m68k v3.16 status update
Date: Wed, 6 Aug 2014 09:35:37 +0200	[thread overview]
Message-ID: <CAMuHMdX-46QGM6T3G_e0RzeTm8vDZ1Ofa2R2w3BQmf_nJxPQLA@mail.gmail.com> (raw)
In-Reply-To: <20140805202904.GA23676@physik.fu-berlin.de>

On Tue, Aug 5, 2014 at 10:29 PM, John Paul Adrian Glaubitz
<glaubitz@physik.fu-berlin.de> wrote:
> On Tue, Aug 05, 2014 at 09:52:58PM +0200, Ingo Jürgensmann wrote:
>> 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...
>
> Add to that the X-Surf100 driver that Michael Karcher wrote [1] but
> unfortunately he hasn't cleaned up the code yet and submitted it for
> inclusion in the mainline kernel.

"May I remind you that patches touching areas outside arch/m68k must be
submitted to the appropriate maintainer (use scripts/get_maintainer.pl)."

The current policy is to not add drivers to the m68k repository if they should
go in through other maintainers.

The Atari ROM Port ISA-based EtherNEC, EtherNAT, and NetUSBee drivers
are there because the Atari ROM Port ISA support originated in the old
Linux/m68k CVS repository.

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-08-06  7:35 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 [this message]
2014-08-06  9:53       ` John Paul Adrian Glaubitz
2014-08-08  8:58   ` Michael Schmitz
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=CAMuHMdX-46QGM6T3G_e0RzeTm8vDZ1Ofa2R2w3BQmf_nJxPQLA@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=debian-68k@lists.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=ij@2014.bluespice.org \
    --cc=karcher@physik.fu-berlin.de \
    --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).