From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, synmyth@gmail.com,
zhangyangjing@gmail.com, wangxiaochen0@gmail.com,
linux-kernel@zh-kernel.org, yaxinsn@163.com
Subject: Re: [PATCH v2]Remove messy code documentations and re-patch them
Date: Sat, 11 Jun 2011 11:12:59 +0800 [thread overview]
Message-ID: <20110611031256.GE2319@gmail.com> (raw)
In-Reply-To: <20110610204703.GB13450@kroah.com>
On Fri, Jun 10, 2011 at 01:47:03PM -0700, Greg KH wrote:
> I need these all as individual emails, with proper descriptions and
> Subject lines, as described in the file,
> Documentation/SubmittingPatches.
>
> Care to resend them in that format so that I can apply them?
It's my pleasure, i have sent them with individual emails and proper
formats and descriptions. If you have any other questions, please
let me know.
Thanks
Harry Wei
prev parent reply other threads:[~2011-06-11 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 13:11 [PATCH v2]Remove messy code documentations and re-patch them Harry Wei
2011-06-10 20:47 ` Greg KH
2011-06-11 3:12 ` Harry Wei [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=20110611031256.GE2319@gmail.com \
--to=jiaweiwei.xiyou@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kernel@zh-kernel.org \
--cc=synmyth@gmail.com \
--cc=wangxiaochen0@gmail.com \
--cc=yaxinsn@163.com \
--cc=zhangyangjing@gmail.com \
/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.