From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "Ramirez Luna, Omar" <omar.ramirez@ti.com>
Cc: Sergei Shtylyov <sshtylyov@mvista.com>,
Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
Tony Lindgren <tony@atomide.com>,
l-o <linux-omap@vger.kernel.org>, David Cohen <dacohen@gmail.com>,
lak <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] OMAP: iovmm: fix SW flags passed by user
Date: Fri, 25 Mar 2011 20:05:57 +0000 [thread overview]
Message-ID: <20110325200557.GA14228@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTikV37gmmf5sRQ98EzOL6K7JNvDy9gfCWbR=747k@mail.gmail.com>
On Fri, Mar 25, 2011 at 12:36:57PM -0500, Ramirez Luna, Omar wrote:
> On Fri, Mar 25, 2011 at 12:30 PM, Sergei Shtylyov <sshtylyov@mvista.com> wrote:
> > Hello.
> >
> > Omar Ramirez Luna wrote:
> >
> >> Commit d038aee24dcd changes iovmm to receive flags specified by user,
> >
> > Please also specify that commit's summary for the human readers. Bare ID
> > is only usable to gitweb...
>
> Here it is the patch, introducing the change:
>
> https://patchwork.kernel.org/patch/620871/
>
> If accepted by Hiroshi, I can update the description making reference
> to this patch instead of commit.
It is a requirement that all descriptions which refer to a commit shall
contain both the commit ID *and* the summary line for that commit.
Failure to ensure that's the case results in rejection of the patch
until it conforms.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-25 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 16:46 [PATCH] OMAP: iovmm: fix SW flags passed by user Omar Ramirez Luna
2011-03-25 17:30 ` Sergei Shtylyov
2011-03-25 17:36 ` Ramirez Luna, Omar
2011-03-25 20:05 ` Russell King - ARM Linux [this message]
2011-03-25 20:14 ` Ramirez Luna, Omar
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=20110325200557.GA14228@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Hiroshi.DOYU@nokia.com \
--cc=dacohen@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=omar.ramirez@ti.com \
--cc=sshtylyov@mvista.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).