mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gregory Haskins" <ghaskins@novell.com>
To: "Thadeu Lima de Souza Cascardo" <cascardo@holoscopio.com>,
	"Jiri Kosina" <jkosina@suse.cz>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] trivial: fix a typo in SHM_SIGNAL config description
Date: Mon, 02 Nov 2009 09:19:25 -0700	[thread overview]
Message-ID: <4AEEC03D0200005A00057D47@sinclair.provo.novell.com> (raw)
In-Reply-To: <alpine.LSU.2.00.0911021653250.4203@wotan.suse.de>

>>> On 11/2/2009 at 10:54 AM, in message
<alpine.LSU.2.00.0911021653250.4203@wotan.suse.de>, Jiri Kosina
<jkosina@suse.cz> wrote: 
> On Fri, 30 Oct 2009, Thadeu Lima de Souza Cascardo wrote:
> 
>> Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
>> ---
>>  lib/Kconfig |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>> 
>> diff --git a/lib/Kconfig b/lib/Kconfig
>> index 272cecf..bfe871d 100644
>> --- a/lib/Kconfig
>> +++ b/lib/Kconfig
>> @@ -207,7 +207,7 @@ config SHM_SIGNAL
>>  	tristate "SHM Signal - Generic shared-memory signaling mechanism"
>>  	default n
>>  	help
>> -	 Provides a shared-memory based signaling mechansim to indicate
>> +	 Provides a shared-memory based signaling mechanism to indicate
>>           memory-dirty notifications between two end-points.
>>  
>>  	 If unsure, say N
> 
> This doesn't apply on top of current Linus' tree. Gregory, I guess you'll 
> be taking this one together with your pile that's currently in -next, 
> right?

Yep, Ill pull it to my tree shortly.  Thanks, all.

-Greg






  reply	other threads:[~2009-11-02 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 21:26 Thadeu Lima de Souza Cascardo
2009-11-02 15:54 ` Jiri Kosina
2009-11-02 16:19   ` Gregory Haskins [this message]
2009-11-02 16:40 ` Gregory Haskins

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=4AEEC03D0200005A00057D47@sinclair.provo.novell.com \
    --to=ghaskins@novell.com \
    --cc=cascardo@holoscopio.com \
    --cc=jkosina@suse.cz \
    --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

all inboxes | Powered by JetHome®