From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pushkar Jambhlekar <pushkar.iit@gmail.com>
Cc: "Stephen Warren" <swarren@wwwdotorg.org>,
"Lee Jones" <lee@kernel.org>, "Eric Anholt" <eric@anholt.net>,
"Michael Zoran" <mzoran@crowfest.net>,
"Daniel Stone" <daniels@collabora.com>,
"Stefan Wahren" <stefan.wahren@i2se.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Stafford Horne" <shorne@gmail.com>,
popcornmix <popcornmix@gmail.com>,
"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
"moderated list:BROADCOM BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@lists.infradead.org>,
"moderated list:BROADCOM BCM2835 ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vc04_services: Fixing coding guideline error
Date: Thu, 16 Mar 2017 15:36:52 +0900 [thread overview]
Message-ID: <20170316063652.GA21167@kroah.com> (raw)
In-Reply-To: <CAMvNc9BT7_5Hu2iFxd1cbEY64jzQxCEZhdgU8cm_p_SDnZFZhQ@mail.gmail.com>
On Thu, Mar 16, 2017 at 11:01:38AM +0530, Pushkar Jambhlekar wrote:
> Any comment?
>
> On Wed, Mar 15, 2017 at 12:01 PM, Pushkar Jambhlekar
One day's response? Hah, give me a few weeks at best for trivial stuff
like this please.
Actually, I totally missed this in my last sweep of staging patches,
because you forgot to include "Staging" in the subject line, so it will
have to wait a few more days at the earliest.
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-16 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 6:31 [PATCH] vc04_services: Fixing coding guideline error Pushkar Jambhlekar
2017-03-16 5:31 ` Pushkar Jambhlekar
2017-03-16 6:36 ` Greg Kroah-Hartman [this message]
2017-03-16 11:40 ` Dan Carpenter
2017-03-21 7:37 ` Greg Kroah-Hartman
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=20170316063652.GA21167@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniels@collabora.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mzoran@crowfest.net \
--cc=noralf@tronnes.org \
--cc=popcornmix@gmail.com \
--cc=pushkar.iit@gmail.com \
--cc=shorne@gmail.com \
--cc=stefan.wahren@i2se.com \
--cc=swarren@wwwdotorg.org \
/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