mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cam Hutchison <camh@xdna.net>
To: thierry.reding@avionic-design.de, linux-kernel@vger.kernel.org
Subject: Re: awful kconfig help texts.
Date: Mon, 20 Aug 2012 12:34:29 +1000 (EST)	[thread overview]
Message-ID: <20120820023429.DB1AE35BC8@xionine.xdna.net> (raw)
In-Reply-To: <20120817061102.GA6003@avionic-0098.adnet.avionic-design.de>

>How about the patch below?

>[...]
>+	  Generic Pulse-Width Modulation (PWM) support.
>+
>+	  In Pulse-Width Modulation, a variation of the width of pulses
>+	  in a rectangular pulse signal is used as a means to alter the
>+	  average power of the signal. Applications include efficient
>+	  power delivery and voltage regulation. In computer systems,
>+	  PWMs are commonly used to control fans or the brightness of
>+	  display backlights.
>+
>+	  This framework provides a generic interface to PWM devices
>+	  within the Linux kernel. On the driver side it provides an API
>+	  to register and unregister a PWM chip, an abstraction of a PWM
>+	  controller, that supports one or more PWM devices. Client
>+	  drivers can request PWM devices and use the generic framework
>+	  to configure as well as enable and disable them.
>+
>+	  The new generic framework replaces the legacy PWM framework
>+	  which allows only a single driver implementing the required
>+	  API. Not all legacy implementations have been ported to the
>+	  new framework yet. The new framework provides an API that is
>+	  backward compatible with the legacy framework so that existing
>+	  client drivers continue to work as expected.

Instead of writing "[Tt]he new framework", write "[Tt]his framework". In 4
years, this will no longer be so new. And when the next framework comes
along, this will look like it is referencing the new one instead of itself.



      parent reply	other threads:[~2012-08-20  2:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 15:16 Dave Jones
2012-07-31 17:07 ` Borislav Petkov
2012-07-31 17:26   ` Steven Rostedt
2012-07-31 17:42     ` Borislav Petkov
2012-08-01  7:47       ` Thierry Reding
2012-08-01  8:56         ` Borislav Petkov
2012-08-01  9:21           ` Lars-Peter Clausen
2012-08-01  9:26             ` Borislav Petkov
2012-08-01  9:38               ` Lars-Peter Clausen
2012-08-01 10:04                 ` Borislav Petkov
2012-08-01 10:56                   ` Lars-Peter Clausen
2012-08-01 12:46                     ` Steven Rostedt
2012-08-01 13:18                       ` Lars-Peter Clausen
2012-08-07 18:25               ` Mark Brown
2012-07-31 18:43   ` Dave Jones
2012-07-31 22:11     ` Borislav Petkov
2012-08-01  7:43   ` Thierry Reding
2012-08-01  9:28     ` Jan Engelhardt
2012-08-16  9:54   ` Thierry Reding
2012-08-16 11:10     ` Borislav Petkov
2012-08-16 12:05       ` Thierry Reding
2012-08-17  6:11         ` Thierry Reding
2012-08-17  7:00           ` Borislav Petkov
2012-08-17  7:19             ` Thierry Reding
2012-08-20  2:34           ` Cam Hutchison [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=20120820023429.DB1AE35BC8@xionine.xdna.net \
    --to=camh@xdna.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thierry.reding@avionic-design.de \
    /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

all inboxes | Powered by JetHome®