From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: Harry Wei <jiaweiwei.xiyou@gmail.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org, trivial@kernel.org,
jkosina@suse.cz, joe@perches.com
Subject: Re: [PATCH] staging/trivial: Fix common spelling mistakes
Date: Sat, 26 Mar 2011 02:39:23 +0100 [thread overview]
Message-ID: <201103260239.23708.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20110315031418.GB3372@gmail.com>
Am Dienstag 15 März 2011, 04:14:20 schrieb Harry Wei:
> > This patch fixes some very common spelling mistakes in drivers/staging
> Hi peter,
> I have sense that you should split this
> patch for patches, which one patch just do
> one spelling mistakes.
>
> But there are so many spelling mistakes.
> I wanna help you with this stuff. Would you
> like to assign some to me. I am so pleasure
> for this.
Hi Harry,
(sorry for my late reply)
thanks for you help and I really appreciate your offer.
I've split up the patch for the staging directory into 27 patches, one for
each affected directory, since this was the easiest way to split my big old
patch ;)
As you know there's still the big "fix common spelling mistakes" patch for the
trivial tree (i.e. everything but the staging directory) which is still
pending, and probably won't apply anymore ;)
So it might be a good idea to split this one up as well, and for this your
help comes handy.
If this is fine with Jiri I'd suggest this splitting:
One patch each for:
arch/
crypto/
fs/
include/
kernel/
lib/
mm/
net/
scripts/
security/
sound/
And for drivers/ one patch for each subsystem/directory,
with the exception of drivers/media/ - this one I'd split into
media/dvb/
media/video/
and the remaining media
If you want to help me the easiest way would be that I update the patch to the
current trivial tree and then send it to you, you apply it with patch (not git
am) and then commit each subdirectory and write a nice commit message and
send it to the list ;)
But I'd like to hear Jiri's opinion first.
Thanks,
Peter
next prev parent reply other threads:[~2011-03-26 1:39 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
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 [this message]
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=201103260239.23708.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=greg@kroah.com \
--cc=jiaweiwei.xiyou@gmail.com \
--cc=jkosina@suse.cz \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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.