From: Parth Sane <laerdevstudios@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org,
driverdev-devel@linuxdriverproject.org, brcnakalin@gmail.com
Subject: Re: [PATCH] staging: netlogic: removed 1 multiple assignment checkpatch warning
Date: Sat, 19 Mar 2016 22:47:13 +0530 [thread overview]
Message-ID: <2CA81717-E9ED-4A50-A871-B05826451778@gmail.com> (raw)
In-Reply-To: <20160319171344.GA26014@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
Hi,
Thanks for getting back to me Greg! I’m still learning, so thanks again for bearing with me!
Regards,
Parth Sane
> On 19-Mar-2016, at 10:43 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Sat, Mar 19, 2016 at 10:04:23PM +0530, Parth Sane wrote:
>> Hi,
>> I haven’t received any feedback as to whether my patch has been accepted. Would request someone to kindly help me out. Maybe you could weigh in here Greg?
>> Regards,
>> Parth Sane
>>> On 15-Mar-2016, at 10:16 PM, laerdevstudios@gmail.com wrote:
>
> 4 days later in the middle of a merge window when I can't add any new
> patches to my queue? Please be patient, I will get to this after
> 4.6-rc1 is out.
>
> thanks,
>
> greg k-h
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
next prev parent reply other threads:[~2016-03-19 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 16:46 [PATCH] staging: netlogic: removed 1 multiple assignment checkpatch warning laerdevstudios
2016-03-19 16:34 ` Parth Sane
2016-03-19 17:03 ` Roger H Newell
2016-03-19 17:09 ` Parth Sane
2016-03-19 17:13 ` Greg KH
2016-03-19 17:17 ` Parth Sane [this message]
2016-03-22 1:53 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2016-03-15 16:23 laerdevstudios
2016-03-15 16:42 ` Greg KH
2016-03-11 9:22 laerdevstudios
2016-03-15 16:09 ` Michal Marek
2016-03-15 16:09 ` Michal Marek
2016-03-11 9:15 laerdevstudios
2016-03-11 9:18 ` Parth Sane
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=2CA81717-E9ED-4A50-A871-B05826451778@gmail.com \
--to=laerdevstudios@gmail.com \
--cc=brcnakalin@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.