All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: cbou@mail.ru
Cc: Andrew Morton <akpm@linux-foundation.org>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kconfig text confusion: Battery Class Support?
Date: Mon, 07 May 2007 09:06:53 +1000	[thread overview]
Message-ID: <1178492813.7731.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20070506202728.GA9520@zarina>

On Mon, 2007-05-07 at 00:27 +0400, Anton Vorontsov wrote:
> Hello Rusty,
> 
> On Sun, May 06, 2007 at 10:06:52PM +1000, Rusty Russell wrote:
> > Hi all,
> > 
> > 	I know writing decent Kconfig help entries is an obscure art, but can
> > we please try harder to make the help, y'know, helpful?  See below for
> > my experience with 2.6.21-mm1.

> Thank you for the message, Rusty. It's "fixed" already in battery2-2.6.git.

Thanks, that sounds much easier to navigate!

Cheers,
Rusty.



      reply	other threads:[~2007-05-06 23:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-06 12:06 Kconfig text confusion: Battery Class Support? Rusty Russell
2007-05-06 20:27 ` Anton Vorontsov
2007-05-06 23:06   ` Rusty Russell [this message]

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=1178492813.7731.13.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=cbou@mail.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.