linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dunlap, Randy" <randy.dunlap@intel.com>
To: "'Maksim Krasnyanskiy'" <maxk@qualcomm.com>,
	esr@thyrsus.com, CML2 <linux-kernel@vger.kernel.org>,
	kbuild-devel@lists.sourceforge.net
Subject: RE: Undocumented configuration symbols in 2.4.6pre2
Date: Wed, 13 Jun 2001 13:19:03 -0700	[thread overview]
Message-ID: <D5E932F578EBD111AC3F00A0C96B1E6F07DBE32F@orsmsx31.jf.intel.com> (raw)

Hi,

Could you make these 5 instances of "Not unsure" be more
palatable and less confusing?

E.g., "Not sure" or "If not sure".
But not the double negative...

As is, it basically says:  "Sure ? say M."

~Randy

> -----Original Message-----
> From: Maksim Krasnyanskiy [mailto:maxk@qualcomm.com]
> 
> >CONFIG_BLUEZ
> >CONFIG_BLUEZ_HCIEMU
> >CONFIG_BLUEZ_HCIUART
> >CONFIG_BLUEZ_HCIUSB
> >CONFIG_BLUEZ_L2CAP
> 
> Here we go:
> 
> CONFIG_BLUEZ
...
> 
>    Say Y here to enable Linux Bluetooth support and to build HCI Core 
>    layer.
> 
...
> 
>    Not unsure ? say N.
> 
> CONFIG_BLUEZ_L2CAP
...
> 
>    Say Y here to compile L2CAP support into the kernel or say 
> M to compile it 
>    as module (l2cap.o).
> 
>    Not unsure ? say M.
> 
> CONFIG_BLUEZ_HCIUART
...
> 
>    Say Y here to compile support for Bluetooth UART devices 
> into the kernel 
>    or say M to compile it as module (hci_uart.o).
> 
>    Not unsure ? say M.
> 
> 
> CONFIG_BLUEZ_HCIUSB
...
> 
>    Say Y here to compile support for Bluetooth USB devices 
> into the kernel 
>    or say M to compile it as module (hci_usb.o).
> 
>    Not unsure ? say M.
> 
> CONFIG_BLUEZ_HCIEMU
...
> 
>    Not unsure ? say M.


             reply	other threads:[~2001-06-13 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 20:19 Dunlap, Randy [this message]
     [not found] <D5E932F578EBD111AC3F00A0C96B1E6F07DBE32F@orsmsx31.jf.intel .com>
2001-06-13 20:51 ` Undocumented configuration symbols in 2.4.6pre2 Maksim Krasnyanskiy
  -- strict thread matches above, loose matches on Subject: below --
2001-06-10 14:09 Eric S. Raymond
2001-06-13 19:35 ` Maksim Krasnyanskiy

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=D5E932F578EBD111AC3F00A0C96B1E6F07DBE32F@orsmsx31.jf.intel.com \
    --to=randy.dunlap@intel.com \
    --cc=esr@thyrsus.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.com \
    /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;
as well as URLs for NNTP newsgroup(s).