From: Joe Perches <joe@perches.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Nicholas Krause <xerofoify@gmail.com>,
gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
aaro.koskinen@iki.fi, pauldaviesc@gmail.com,
nitinkuppelur@gmail.com, linux-kernel@vger.kernel.org,
br@ahlamon.org
Subject: Re: [PATCH 1/2] octeon-usb:Fix coding style issue with space between function name and opening bracket
Date: Tue, 24 Mar 2015 06:20:25 -0700 [thread overview]
Message-ID: <1427203225.5642.5.camel@perches.com> (raw)
In-Reply-To: <20150324130045.GE16501@mwanda>
On Tue, 2015-03-24 at 16:00 +0300, Dan Carpenter wrote:
> On Tue, Mar 24, 2015 at 08:08:16AM -0400, Nicholas Krause wrote:
> > Just one more question, is that patch going to be merged or should I resubmit
> > it as a series of one patch?
> Don't resubmit. Wait for Greg to mail you. It can take a several weeks
> because he is busy.
What Dan said is certainly true, but if after 4 or
more weeks with no reply, I think it's fine to
resubmit or send a polite "ping" requesting status.
There really no other option as no other feedback
mechanism exists and things can and do get lost in
high-volume process.
next prev parent reply other threads:[~2015-03-24 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1427069076-26720-1-git-send-email-xerofoify@gmail.com>
2015-03-23 10:40 ` [PATCH 1/2] octeon-usb:Fix coding style issue with space between function name and opening bracket Dan Carpenter
[not found] ` <8FDBB6BF-55C6-44B5-A645-147F1BEAF388@gmail.com>
2015-03-23 13:06 ` Dan Carpenter
[not found] ` <B6E63034-68D1-4728-B8C5-71BE94A1CFE3@gmail.com>
2015-03-24 7:08 ` Dan Carpenter
[not found] ` <15C5DCA5-565D-4E38-B247-4F18FF04930F@gmail.com>
2015-03-24 13:00 ` Dan Carpenter
2015-03-24 13:20 ` Joe Perches [this message]
2015-03-24 20:29 ` Aaro Koskinen
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=1427203225.5642.5.camel@perches.com \
--to=joe@perches.com \
--cc=aaro.koskinen@iki.fi \
--cc=br@ahlamon.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nitinkuppelur@gmail.com \
--cc=pauldaviesc@gmail.com \
--cc=xerofoify@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;
as well as URLs for NNTP newsgroup(s).