public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruce Harada <bruce@ask.ne.jp>
To: Bjorn Wesen <bjorn.wesen@axis.com>
Cc: esr@thyrsus.com, linux-kernel@vger.kernel.org,
	kbuild-devel@lists.sourceforge.net
Subject: Re: Only 5 undocumented configuration symbols left
Date: Thu, 31 May 2001 20:28:20 +0900	[thread overview]
Message-ID: <20010531202820.0ac5bf9d.bruce@ask.ne.jp> (raw)
In-Reply-To: <Pine.LNX.4.21.0105311213261.28884-100000@godzilla.axis.se>
In-Reply-To: <20010530190744.A2027@thyrsus.com> <Pine.LNX.4.21.0105311213261.28884-100000@godzilla.axis.se>


Since I don't actually know what you're talking about, I'll just make picky
little comments about the grammar, etc. ;)

On Thu, 31 May 2001 12:14:06 +0200 (CEST)
Bjorn Wesen <bjorn.wesen@axis.com> wrote:

> +Etrax100 I2C configuration
> +CONFIG_ETRAX_I2C_USES_PB_NOT_PB_I2C
> +  Select whether to use the special I2C mode in the PB I/O register or
> +  not. This option needs to be selected in order to use some drivers that
> +  accesses the I2C I/O pins directly instead of going through the I2C
     ^^^^^^^^
     access

> +  driver, like the DS1302 realtime-clock driver. If you are uncertain, 
> +  choose yes here.
     ^^^^^^^^^^^^^^^
This is usually "say Y here." Minor, I know, but it'd be nice to get the
nomenclature standardized.

(Actually, "...to be selected in order to use some drivers, such as the DS1302
realtime clock driver, that access the I2C I/O pins directly instead of going
through the I2C driver." might scan better.)


Bruce



  reply	other threads:[~2001-05-31 11:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-30 23:07 Only 5 undocumented configuration symbols left Eric S. Raymond
2001-05-31 10:14 ` Bjorn Wesen
2001-05-31 11:28   ` Bruce Harada [this message]
2001-05-31 13:27 ` Tom Gall

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=20010531202820.0ac5bf9d.bruce@ask.ne.jp \
    --to=bruce@ask.ne.jp \
    --cc=bjorn.wesen@axis.com \
    --cc=esr@thyrsus.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@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