public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Thorsten Glaser <tg@mirbsd.de>
To: linux-m68k@vger.kernel.org
Subject: Re: [PATCH 1/1] m68k: add missing I/O macros {in,out}{w,l}_p() for !CONFIG_ISA
Date: Mon, 4 Oct 2010 14:13:35 +0000 (UTC)	[thread overview]
Message-ID: <loom.20101004T161145-690@post.gmane.org> (raw)
In-Reply-To: AANLkTim_gdMc5scQm-oAD6Jowv6q=W0bK=rkjZUmAgLd@mail.gmail.com

Geert Uytterhoeven <geert <at> linux-m68k.org> writes:

> I am questioning a distro building staging drivers for m68k.
> IMHO it's a waste of CPU cycles (especially for native builds).

Yeah. However, I don’t speak for the kernel team. I’m “just”
someone playing buildd, until they can do that automatedly
again (after getting new kernel+gcc+eglibc). It’s annoying
to me, too (just how much longer do I need to wait?).

bye,
//mirabilos
-- 
«MyISAM tables -will- get corrupted eventually. This is a fact of life. »
“mysql is about as much database as ms access” – “MSSQL at least descends
from a database” “it's a rebranded SyBase” “MySQL however was born from a
flatfile and went downhill from there” – “at least jetDB doesn’t claim to
be a database”  (#nosec)    ‣‣‣ Please let MySQL and MariaDB finally die!

  reply	other threads:[~2010-10-04 14:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-03 18:38 [PATCH 0/1] m68k: add missing I/O macros {in,out}{w,l}_p() for !CONFIG_ISA Thorsten Glaser
2010-10-03 18:48 ` [PATCH 1/1] " Thorsten Glaser
2010-10-04  0:51   ` Finn Thain
2010-10-04  7:40     ` Thorsten Glaser
2010-10-04  8:47       ` Finn Thain
2010-10-04  9:10         ` Thorsten Glaser
2010-10-04 10:22           ` Finn Thain
2010-10-04 11:30             ` Thorsten Glaser
2010-10-04 13:18             ` Geert Uytterhoeven
2010-10-04 13:33               ` Finn Thain
2010-10-04 13:40               ` Thorsten Glaser
2010-10-04 14:01                 ` Geert Uytterhoeven
2010-10-04 14:13                   ` Thorsten Glaser [this message]
2010-10-04 19:20                   ` Thorsten Glaser
2010-10-13 20:17                   ` Thorsten Glaser
2010-10-05 12:56                 ` Stephen R. Marenka
2010-10-05 14:10                   ` debian kernel config, was " Finn Thain
2010-10-06  0:57                   ` Stephen R. Marenka
2010-10-06  9:26                   ` Thorsten Glaser
2010-10-06 13:09                     ` Stephen R. Marenka
2010-10-06 14:15                     ` Finn Thain
2010-10-04  7:57   ` Michael Schmitz
2010-10-04  8:13     ` Thorsten Glaser
2010-10-04  9:08       ` Finn Thain
2010-10-04 10:18         ` Thorsten Glaser
2010-10-04 10:51           ` Finn Thain
2010-10-04 11:37             ` Thorsten Glaser
2010-10-04 12:45               ` Finn Thain
2010-10-16 17:12   ` 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=loom.20101004T161145-690@post.gmane.org \
    --to=tg@mirbsd.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