From: "Sharma, Sanjeev" <Sanjeev_Sharma@mentor.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"swetland@google.com" <swetland@google.com>,
"waydi1@gmail.com" <waydi1@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"daniel@ffwll.ch" <daniel@ffwll.ch>
Subject: RE: [PATCH] staging: android: Fixed missing blank line
Date: Mon, 28 Jul 2014 05:14:47 +0000 [thread overview]
Message-ID: <FDC088D3B5555644AE135ED28A7ABDE938F04F7F@EU-MBX-04.mgc.mentorg.com> (raw)
In-Reply-To: <20140723152512.GA28295@kroah.com>
Hello Greg,
I didn't received automated email.
Regards
Sanjeev Sharma
-----Original Message-----
From: Greg KH [mailto:gregkh@linuxfoundation.org]
Sent: Wednesday, July 23, 2014 8:55 PM
To: Sharma, Sanjeev
Cc: devel@driverdev.osuosl.org; swetland@google.com; waydi1@gmail.com; linux-kernel@vger.kernel.org; daniel@ffwll.ch
Subject: Re: [PATCH] staging: android: Fixed missing blank line
On Wed, Jul 23, 2014 at 10:08:44AM +0000, Sharma, Sanjeev wrote:
> Thanks, so this is also available in next kernel release version.
I don't understand the question. You should have gotten an automated email when the patch was applied that explained where the patch was now located, and when it would be merged into Linus's tree. Did you not get that?
greg k-h
next prev parent reply other threads:[~2014-07-28 5:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 4:47 [PATCH] staging: android: Fixed missing blank line Sanjeev Sharma
2014-07-18 23:16 ` Greg KH
2014-07-23 10:08 ` Sharma, Sanjeev
2014-07-23 15:25 ` Greg KH
2014-07-28 5:14 ` Sharma, Sanjeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-17 7:18 sanjeev sharma
2014-07-17 7:28 ` Dan Carpenter
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=FDC088D3B5555644AE135ED28A7ABDE938F04F7F@EU-MBX-04.mgc.mentorg.com \
--to=sanjeev_sharma@mentor.com \
--cc=daniel@ffwll.ch \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swetland@google.com \
--cc=waydi1@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).