From: "Ingo Jürgensmann" <ij@2013.bluespice.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
Debian m68k <debian-68k@lists.debian.org>,
Michael Schmitz <schmitzmic@gmail.com>
Subject: Re: [RFC] m68k: Update defconfigs for v3.9
Date: Thu, 23 May 2013 22:28:46 +0200 [thread overview]
Message-ID: <C99A4D13-CF11-49A8-9CEE-A3FB8563509F@2013.bluespice.org> (raw)
In-Reply-To: <CAMuHMdVSqN6Bjn1Ph-8xzZ64HzAcj7oBA8B3GNE8PTessUzBkQ@mail.gmail.com>
Am 23.05.2013 um 21:19 schrieb Geert Uytterhoeven <geert@linux-m68k.org>:
> I pushed out an RFC for a long-overdue update of the m68k defconfig
> files to my defconfig branch:
> https://git.kernel.org/cgit/linux/kernel/git/geert/linux-m68k.git/commit/?h=defconfig&id=417ed3fbd7bcc4e909421d35984947d6e45009bb
> [...]
Looks good for me for Amiga, as far as I can tell in a hurry...
> I really hope to push this into mainline this time, and start to update the
> defconfigs again every kernel release.
> Any comments are welcome! Thanks!
I'm just waiting for the support for Blizzard SCSI Support (ESP), but this should be the only thing I'm missing for now.
Maybe cbmuser and twice11 can help Michael in porting the driver when Elgar finally got relocated to the FU Berlin?
--
Ciao... // Fon: 0381-2744150
Ingo \X/ http://blog.windfluechter.net
gpg pubkey: http://www.juergensmann.de/ij_public_key.asc
next prev parent reply other threads:[~2013-05-23 20:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 19:19 [RFC] m68k: Update defconfigs for v3.9 Geert Uytterhoeven
2013-05-23 20:28 ` Ingo Jürgensmann [this message]
2013-05-25 9:01 ` Michael Schmitz
2013-05-25 11:15 ` Thorsten Glaser
2013-05-24 7:27 ` Finn Thain
2013-05-24 10:54 ` Laurent Vivier
2013-05-25 8:04 ` Finn Thain
2013-05-24 12:59 ` Geert Uytterhoeven
2013-05-24 13:06 ` Geert Uytterhoeven
2013-05-25 8:06 ` Finn Thain
2013-05-25 19:33 ` Brad Boyer
2013-05-25 19:47 ` Ingo Jürgensmann
2013-05-26 7:53 ` Geert Uytterhoeven
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=C99A4D13-CF11-49A8-9CEE-A3FB8563509F@2013.bluespice.org \
--to=ij@2013.bluespice.org \
--cc=debian-68k@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.