From: Finn Thain <fthain@telegraphics.com.au>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: 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 20:08:26 +1100 (EST) [thread overview]
Message-ID: <alpine.OSX.2.00.1010041955060.285@localhost> (raw)
In-Reply-To: <Pine.BSM.4.64L.1010040809360.8491@herc.mirbsd.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 938 bytes --]
On Mon, 4 Oct 2010, Thorsten Glaser wrote:
> Besides, it’s easier to get a bunch of modules that don’t do anything
> except say the hardware they steer isn’t available to compile than to
> change the config
Which modules are we talking about? In 2.6.32-23, debian patches speakup
into drivers/staging but I don't see it in mainline drivers/accessibility
or drivers/staging.
If the bug is not in the mainline, then the fix should arguably be
downstream too. (Policy seems to be that the mainline doesn't carry code
that doesn't have in-tree users.)
> (especially as the latter potentially has to be done for every new
> kernel version, and I’d rather keep things working, as they seem to
> change very quickly and nobody can keep up really).
Is it easier to maintain local patches from one debian release to another
than it is to maintain .config changes?
Finn
>
> bye,
> //mirabilos
>
next prev parent reply other threads:[~2010-10-04 9:08 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
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 [this message]
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=alpine.OSX.2.00.1010041955060.285@localhost \
--to=fthain@telegraphics.com.au \
--cc=linux-m68k@vger.kernel.org \
--cc=tg@mirbsd.de \
/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.