From: Greg KH <gregkh@linuxfoundation.org>
To: Ranjith T <ranjithece24@gmail.com>
Cc: devel@driverdev.osuosl.org, Ian Abbott <abbotti@mev.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] comedi: driver: Fix - BIT macro used coding style issue
Date: Fri, 6 Nov 2015 08:51:10 -0800 [thread overview]
Message-ID: <20151106165110.GA23622@kroah.com> (raw)
In-Reply-To: <CAEgNZo_E2sw+oGmnTe8PLxabmRRqdaaPofvrke=u1z+Mb6hHSw@mail.gmail.com>
On Fri, Nov 06, 2015 at 07:24:18PM +0530, Ranjith T wrote:
> Is this patch is fine?..Because I didn't get any reply for this patch
You sent it 1 day ago, while we are in the middle of the merge window
and I can't touch anything for 2 weeks at the earliest.
Please be patient.
greg k-h
next prev parent reply other threads:[~2015-11-06 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 15:57 [PATCH 3/3] comedi: driver: Fix - BIT macro used coding style issue Ranjith
2015-11-06 13:54 ` Ranjith T
2015-11-06 15:08 ` Ian Abbott
2015-11-06 16:51 ` Greg KH [this message]
2015-11-06 20:21 ` 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=20151106165110.GA23622@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ranjithece24@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