From: Greg KH <greg@kroah.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Mark Allyn <mark.a.allyn@intel.com>,
linux-kernel@vger.kernel.org, alan@linux.intel.com,
charles.f.johnson@intel.com
Subject: Re: Introduction to rar_register patch set of 5 patches
Date: Fri, 22 Jan 2010 10:33:22 -0800 [thread overview]
Message-ID: <20100122183322.GA9512@kroah.com> (raw)
In-Reply-To: <20100122102308.bb17fd1a.rdunlap@xenotime.net>
On Fri, Jan 22, 2010 at 10:23:08AM -0800, Randy Dunlap wrote:
> On Fri, 22 Jan 2010 09:53:30 -0800 Mark Allyn wrote:
>
> > The following five patches are for the Restricted Access Region
> > Register (rar_register) driver.
> >
> > This driver is for the Intel MID platform.
>
> Hi Mark,
>
> Please read and try to follow Documentation/SubmittingPatches.
>
> E.g.:
>
> "The canonical patch subject line is:
>
> Subject: [PATCH 001/123] subsystem: summary phrase"
>
> so your patch 1 should be more like:
>
> [PATCH 1/5] rar_register: rename rar_driver to rar_register
>
> and then that one patch's description should be at the top of that
> email's body, not in the patch introduction/cover email.
>
> As it stands, these 5 patch descriptions need to be moved
> to each patch's patch description...
I agree, I can not apply these as-is.
Mark, please redo the patches.
Hint, we do have tools that make this much easier, like quilt and git,
you might take the time to learn to use them so that future patch
submissions are not bungled as badly as these have been.
thanks,
greg k-h
next prev parent reply other threads:[~2010-01-22 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 17:53 Introduction to rar_register patch set of 5 patches Mark Allyn
2010-01-22 18:23 ` Randy Dunlap
2010-01-22 18:33 ` Greg KH [this message]
2010-01-22 19:59 ` Allyn, Mark A
2010-01-22 20:35 ` Greg KH
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=20100122183322.GA9512@kroah.com \
--to=greg@kroah.com \
--cc=alan@linux.intel.com \
--cc=charles.f.johnson@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.a.allyn@intel.com \
--cc=rdunlap@xenotime.net \
/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