From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>
Cc: balbi@ti.com, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] arm/davinci/musb: fix mispint introduced by commit 032ec49f5351e9cb242b1a1c367d14415043ab95
Date: Sat, 22 Dec 2012 21:52:47 +0400 [thread overview]
Message-ID: <50D5F36F.3070707@mvista.com> (raw)
In-Reply-To: <20121221090625.GA31453@arwen.pp.htv.fi>
Hello.
On 21-12-2012 13:06, Felipe Balbi wrote:
> please respin this patch with a real commit log.
And then, when referring to commit ID that broke da8xx.c don't forget to
also specify the commit summmary in parens (or however you like).
>> Signed-off-by: Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>
WBR, Sergei
next prev parent reply other threads:[~2012-12-22 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 21:59 [PATCH] arm/davinci/musb: fix mispint introduced by commit 032ec49f5351e9cb242b1a1c367d14415043ab95 Mikhail Kshevetskiy
2012-12-21 9:06 ` Felipe Balbi
2012-12-22 17:52 ` Sergei Shtylyov [this message]
2013-01-05 18:50 ` Sergei Shtylyov
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=50D5F36F.3070707@mvista.com \
--to=sshtylyov@mvista.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mikhail.kshevetskiy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox