linux-kernel - Re: [PATCH] staging/trivial: Fix common spelling mistakes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110314224746.GA21100@kroah.com>
Date:	Mon, 14 Mar 2011 15:47:46 -0700
From:	Greg KH <greg@...ah.com>
To:	Peter Hüwe <PeterHuewe@....de>
Cc:	Greg KH <gregkh@...e.de>, devel@...uxdriverproject.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging/trivial: Fix common spelling mistakes

On Mon, Mar 14, 2011 at 11:43:23PM +0100, Peter Hüwe wrote:
> Am Montag 14 März 2011, 23:03:13 schrieb Greg KH:
> > On Mon, Mar 14, 2011 at 10:57:55PM +0100, Peter Huewe wrote:
> > > This patch fixes some very common spelling mistakes in drivers/staging
> > 
> > Unfortunatly, I've applied a bunch of patches since the last linux-next
> > tree.
> > 
> > It would be nice if I could have taken a bunch of these changes, and if
> > it was broken up into individual patches (each either doing only one
> > spelling change, or only operating on one driver/file) then I could
> > have.  But as it is, I can't :(
> > 
> > So, another reason it makes sense to break patches up into the logical
> > pieces.  Please do this and resend.
> 
> Absolutely no problem, Greg. 
> I thought since it is only a simple spellcheck in comments one big spellcheck 
> patch would be logical enough.
> 
> I could split up by driver/directory with reasonable effort - would this be 
> okay with you? Or do you want per file?
> Or do you prefer the changes split by each spelling change?

Either is fine, but you need to split it up somehow please.  Whatever is
easier for you.

> I can recreate the patch(es) however you like them - so just tell me your 
> preference.
> 
> Where can I find you current tree so I can patch against this one?

As per the MAINTAINERS file:
	STAGING SUBSYSTEM
	M:      Greg Kroah-Hartman <gregkh@...e.de>
	T:      git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6.git

Use the staging-next branch please.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/