public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: esr@thyrsus.com
Cc: Russell King <rmk@arm.linux.org.uk>,
	CML2 <linux-kernel@vger.kernel.org>,
	kbuild-devel@lists.sourceforge.net
Subject: Re: Missing help entries in 2.4.6pre5
Date: Fri, 22 Jun 2001 15:54:53 +0100	[thread overview]
Message-ID: <18157.993221693@redhat.com> (raw)
In-Reply-To: <20010622102458.A13435@thyrsus.com>
In-Reply-To: <20010622102458.A13435@thyrsus.com>  <20010622094934.A13075@thyrsus.com> <20010621160309.A6744@thyrsus.com> <20010621154934.A6582@thyrsus.com> <20010621205537.X18978@flint.arm.linux.org.uk> <20010621160309.A6744@thyrsus.com> <7987.993197604@redhat.com> <20010622094934.A13075@thyrsus.com> <10604.993218210@redhat.com>


esr@thyrsus.com said:
>  From the person(s) reponsible for the missing symbols, I want
> documentation.  The problem is that, lacking a detailed database of
> who is responsible for what, I don't know how to prod each of the
> people I really want to supplicate/irritate without having you see it
> also.

In fact, in the case of the Ocelot and IQ80310, I _am_ the person 
responsible for their visibility in Linus' tree at the moment, so you
shouldn't be hassling the owners of those symbols.

I put the references there, as guards for drivers which are specific to
those platforms, although the rest of the support for those platforms hasn't
yet been merged into Linus' tree.

Until such time as the {Strong,}ARM and MIPS arch maintainers feed the rest 
of the code to support these platforms to Linus, it's unfair to hassle them
for the documentation. And until that time, it's not strictly necessary 
either, because the user can't even see the options in question, surely?

You could perhaps argue that I shouldn't have sent code to Linus which 
can't yet be enabled and used. If you did, I'd disagree with that.

The VIRTUAL_ER option is also my fault, and will go away shortly - it just
depends on how many times I have to resend the patch to Linus.

--
dwmw2



  parent reply	other threads:[~2001-06-22 14:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010622111154.A13799@thyrsus.com>
2001-06-21 19:49 ` Missing help entries in 2.4.6pre5 Eric S. Raymond
2001-06-21 19:55   ` Russell King
2001-06-21 20:03     ` Eric S. Raymond
2001-06-22  8:13     ` David Woodhouse
2001-06-22 13:49       ` Eric S. Raymond
2001-06-22 13:47         ` Russell King
2001-06-22 13:54           ` Eric S. Raymond
2001-06-22 13:54             ` Russell King
2001-06-22 14:28               ` Brent D. Norris
2001-06-22 14:00         ` Wichert Akkerman
2001-06-22 14:13           ` Rob Landley
2001-06-24  0:05           ` David Woodhouse
2001-06-22 15:43         ` Alan Cox
2001-06-22 16:01           ` Eric S. Raymond
2001-06-22 13:56       ` David Woodhouse
2001-06-22 14:24         ` Eric S. Raymond
2001-06-22 14:54         ` David Woodhouse [this message]
2001-06-22 16:27           ` David Woodhouse
2001-06-22 17:12             ` Eric S. Raymond
2001-06-21 22:22   ` Nicolas Pitre
2001-06-21 22:40     ` Russell King
2001-06-21 22:51       ` Eric S. Raymond
2001-06-22  8:24       ` David Woodhouse
2001-06-22 13:51         ` Eric S. Raymond
2001-06-22  2:15     ` Eric S. Raymond
2001-06-22 14:47 Holzrichter, Bruce

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=18157.993221693@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=esr@thyrsus.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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