From: Greg KH <gregkh@linuxfoundation.org>
To: Kumar Gaurav <kumargauravgupta3@gmail.com>
Cc: devel@driverdev.osuosl.org, lidza.louina@gmail.com,
driverdev-devel@linuxdriverproject.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging:dgap:dgap_tty.c: Upgraded driver to use Mutex instead of semaphore
Date: Sun, 20 Apr 2014 15:28:13 +0000 [thread overview]
Message-ID: <20140420152813.GA20165@kroah.com> (raw)
In-Reply-To: <535351CA.8000201@gmail.com>
On Sun, Apr 20, 2014 at 10:19:14AM +0530, Kumar Gaurav wrote:
> Hi All,
>
> Any update on below patch. Do i need to make any modification?
Please give an overworked maintainer a chance to catch up on his email.
If after a week you haven't heard anything, then ask again.
thanks,
greg k-h
next prev parent reply other threads:[~2014-04-20 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 15:55 [PATCH] Staging:dgap:dgap_tty.c: Upgraded driver to use Mutex instead of semaphore Kumar Gaurav
2014-04-20 4:50 ` Kumar Gaurav
2014-04-20 15:28 ` Greg KH [this message]
2014-04-22 9:45 ` 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=20140420152813.GA20165@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kumargauravgupta3@gmail.com \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@vger.kernel.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