From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: Greg KH <greg@kroah.com>
Cc: Greg KH <gregkh@suse.de>,
devel@linuxdriverproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/trivial: Fix common spelling mistakes
Date: Mon, 14 Mar 2011 23:43:23 +0100 [thread overview]
Message-ID: <201103142343.23504.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20110314220313.GA21204@kroah.com>
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?
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?
Thanks,
Peter
(p.s.:sorry for not hitting reply to all)
next prev parent reply other threads:[~2011-03-14 22:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 13:18 [PATCH] trivial: fix common spelling mistakes Peter Huewe
2011-01-06 14:01 ` Jesper Juhl
2011-01-06 14:14 ` Peter Hüwe
2011-01-07 10:04 ` Jiri Kosina
2011-01-07 13:38 ` Peter Hüwe
2011-03-08 22:49 ` [PATCH v2/resend] " Peter Huewe
2011-03-14 12:00 ` Jiri Kosina
2011-03-14 20:35 ` [PATCH v3] " Peter Huewe
2011-03-14 21:57 ` [PATCH] staging/trivial: Fix " Peter Huewe
2011-03-14 22:03 ` Greg KH
2011-03-14 22:43 ` Peter Hüwe [this message]
2011-03-14 22:47 ` Greg KH
2011-03-26 1:17 ` [PATCH 0/27] " Peter Huewe
2011-03-26 1:17 ` [PATCH 01/27] staging/ath6kl: " Peter Huewe
2011-03-26 1:17 ` [PATCH 02/27] staging/bcm: " Peter Huewe
2011-03-26 1:17 ` [PATCH 03/27] staging/brcm80211: " Peter Huewe
2011-03-26 1:17 ` [PATCH 04/27] staging/comedi: " Peter Huewe
2011-03-26 1:17 ` [PATCH 05/27] staging/crystalhd: " Peter Huewe
2011-03-26 1:17 ` [PATCH 06/27] staging/dt3155v4l: " Peter Huewe
2011-03-26 1:17 ` [PATCH 07/27] staging/easycap: " Peter Huewe
2011-03-15 3:14 ` [PATCH] staging/trivial: " Harry Wei
2011-03-26 1:39 ` Peter Hüwe
2011-03-26 2:21 ` Harry Wei
2011-03-15 2:58 ` [PATCH v2/resend] trivial: fix " Harry Wei
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=201103142343.23504.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=devel@linuxdriverproject.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--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.