public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: Future of linux-arch
Date: Sun, 28 Mar 2004 21:48:19 +0100	[thread overview]
Message-ID: <20040328214819.F10358@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040328122920.404e5b37.davem@redhat.com>; from davem@redhat.com on Sun, Mar 28, 2004 at 12:29:20PM -0800

On Sun, Mar 28, 2004 at 12:29:20PM -0800, David S. Miller wrote:
> See, because this patch goes beyond arch issues, driver folks have to use
> these interfaces, so logically it appears that folks outside of the arch
> community should contribute to the design and review of said interfaces.

So this is the thanks for taking hold of an issue which someone else
raised and trying to get it sorted.  Fine.

But that's no good if we can't even present what we think is a good
interface from the architecture side.  Which it appears we still
can't.

Remember that it was Andrea who raised it on lkml and it moved to
to linux-arch because all the architecture people needed to be
involved?

Well, I'm sick to death with this issue.  Someone else can sort out
this problem.  I'm going to just do what's necessary to sort it on
ARM and leave it at that.  If that screws someone else, tough shit.
I've made the effort and done my best to find a reasonable solution.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-03-28 20:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-28 11:01 Future of linux-arch Russell King
2004-03-28 20:29 ` David S. Miller
2004-03-28 20:48   ` Russell King [this message]
2004-03-28 20:55     ` David S. Miller

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=20040328214819.F10358@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=davem@redhat.com \
    --cc=linux-arch@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