Linux M68K Architecture development
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Debian m68k <debian-68k@lists.debian.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: debian-installer progress and input needed
Date: Mon, 22 May 2017 10:09:32 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1705221001520.1844@nippy.intranet> (raw)
In-Reply-To: <242cd92a-e660-088e-6656-393dbcf74792@physik.fu-berlin.de>

On Sun, 21 May 2017, John Paul Adrian Glaubitz wrote:

> On 05/17/2017 02:24 PM, John Paul Adrian Glaubitz wrote:
> > Ok, let's get some order into this.
> > 
> > I have already opened a bug report to include loop-modules [1].
> > 
> > Then, looking at the module packages on m68k [2] and powerpc [3],
> > I suggest to add the following new packages first:
> > (...)
> > Did I miss anything?
> 
> I have made some changes to src:linux now following the previous discussion
> and I have pushed them to github [1].
> 
> Comments?
> 

Looks good but I suspect that macmace needs to be added to the nic-modules 
list.

-- 

> Adrian
> 
> > [1] https://github.com/glaubitz/linux-debian/commits/m68k
> 
> 

  reply	other threads:[~2017-05-22  0:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 21:21 debian-installer progress and input needed John Paul Adrian Glaubitz
2017-05-16  7:40 ` Geert Uytterhoeven
2017-05-16  8:25   ` Laurent Vivier
2017-05-16  8:13 ` Finn Thain
2017-05-17 12:24 ` John Paul Adrian Glaubitz
2017-05-18  5:37   ` Michael Schmitz
2017-05-21 11:33   ` John Paul Adrian Glaubitz
2017-05-22  0:09     ` Finn Thain [this message]
2017-05-22  9:39       ` John Paul Adrian Glaubitz

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=alpine.LNX.2.00.1705221001520.1844@nippy.intranet \
    --to=fthain@telegraphics.com.au \
    --cc=debian-68k@lists.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --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