From: Malcolm Priestley <tvboxspy@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 4/5] staging: vt6656: Remove variable fKillEventPollingThread
Date: Tue, 18 Feb 2014 20:22:31 +0000 [thread overview]
Message-ID: <5303C107.9060309@gmail.com> (raw)
In-Reply-To: <20140218190046.GA20757@kroah.com>
On 18/02/14 19:00, Greg KH wrote:
> On Mon, Feb 17, 2014 at 09:24:33PM +0000, Malcolm Priestley wrote:
>> We already kill the urb and since patch
>> s_nsInterruptUsbIoCompleteRead add urb status returns.
>> have error handling
>>
>> There is no need for this variable.
>>
>> Signed-off-by: Malcolm Priestley <tvboxspy@gmail.com>
>>
>> Conflicts:
>> drivers/staging/vt6656/usbpipe.c
>
> Why is this in your Changelog entry?
>
Oh sorry, I should have deleted it.
It was cherry picked from another git branch where patch 1
didn't exist and was fixed.
prev parent reply other threads:[~2014-02-18 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 21:24 [PATCH 4/5] staging: vt6656: Remove variable fKillEventPollingThread Malcolm Priestley
2014-02-18 19:00 ` Greg KH
2014-02-18 20:22 ` Malcolm Priestley [this message]
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=5303C107.9060309@gmail.com \
--to=tvboxspy@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).