public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test7 and HIDBP
Date: Sat, 11 Oct 2003 19:10:50 +0900	[thread overview]
Message-ID: <242001c38fdf$fb165690$5cee4ca5@DIAMONDLX60> (raw)
In-Reply-To: 20031010073750.001ad559.rddunlap@osdl.org

Randy Dunlap replied to me:

> | OK, I already know that I'm half-blind, but now either I'm 75% blind or
> | else these are facts:
> |    make xconfig has options for HIDBP.
> |    make gconfig doesn't.
> | Of course I want full HID so this might not matter, but I have memories
> | of needing HIDBP a few years ago.
>
> I don't know about gconfig, but you don't want or need HIDBP with full
> HID.

Indeed I don't want or need HIDBP with full HID, which is the reason I said
"so this might not matter".  Also I don't know if anyone still needs HIDBP
or not, which is the reason I said "I have memories of needing HIDBP a few
years ago".

Surely if anyone does still need HIDBP then it should be added to gconfig?
Surely if no one needs HIDBP any more then it should be deleted entirely?

Or maybe I'm 75% blind, maybe I it really is in gconfig and I couldn't see
it.  But no one has said that this is the case.


  reply	other threads:[~2003-10-11 10:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10  9:34 2.6.0-test7 and HIDBP Norman Diamond
2003-10-10 14:37 ` Randy.Dunlap
2003-10-11 10:10   ` Norman Diamond [this message]
2003-10-11 11:13     ` Sam Ravnborg
2003-10-11 13:15       ` Norman Diamond
2003-10-13 16:49         ` Randy.Dunlap
2003-10-13 16:59           ` Randy.Dunlap
2003-10-13 17:50         ` Roman Zippel
2003-10-15 10:23           ` Norman Diamond
  -- strict thread matches above, loose matches on Subject: below --
2003-10-14  3:56 Randy.Dunlap

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='242001c38fdf$fb165690$5cee4ca5@DIAMONDLX60' \
    --to=ndiamond@wta.att.ne.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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