From: Tony Cho <tony.cho@atmel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <devel@driverdev.osuosl.org>, <linux-wireless@vger.kernel.org>,
<johnny.kim@atmel.com>, <chris.park@atmel.com>,
<rachel.kim@atmel.com>, <glen.lee@atmel.com>, <leo.kim@atmel.com>,
<austin.shin@atmel.com>, <adel.noureldin@atmel.com>,
<adham.abozaeid@atmel.com>, <Nicolas.FERRE@atmel.com>
Subject: Re: [PATCH 2/2] staging: wilc1000: remove RX_BH_TYPE
Date: Wed, 16 Sep 2015 10:19:44 +0900 [thread overview]
Message-ID: <55F8C3B0.8000902@atmel.com> (raw)
In-Reply-To: <20150915133103.GA18036@kroah.com>
Hi Greg,
If it's already in your tree and can be applied alone, no problem to me. I will later send remaining series of it.
Thanks,
Tony.
On 2015년 09월 15일 22:31, Greg KH wrote:
> On Tue, Sep 15, 2015 at 10:17:41AM +0900, Tony Cho wrote:
>> Hi Greg,
>>
>> I am sorry but please ignore this patch in this time.
> It's already in my tree, right? I can revert it if you want me to, but
> I can't ignore it anymore, sorry.
>
> greg k-h
next prev parent reply other threads:[~2015-09-16 1:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 7:52 [PATCH 1/7] staging: wilc1000: remove PANDA_BOARD Tony Cho
2015-09-11 7:52 ` [PATCH 2/2] staging: wilc1000: remove RX_BH_TYPE Tony Cho
2015-09-15 1:17 ` Tony Cho
2015-09-15 13:31 ` Greg KH
2015-09-16 1:19 ` Tony Cho [this message]
2015-09-11 7:52 ` [PATCH 2/7] staging: wilc1000: remove useless define PHY_802_11n Tony Cho
2015-09-11 7:52 ` [PATCH 3/7] staging: wilc1000: remove unnecessary define FIVE_GHZ_BAND Tony Cho
2015-09-11 7:53 ` [PATCH 4/7] staging: wilc1000: remove unused defines Tony Cho
2015-09-11 7:53 ` [PATCH 5/7] staging: wilc1000: remove unnecessary extern function declaration Tony Cho
2015-09-11 7:53 ` [PATCH 6/7] staging: wilc1000: delete unused global variables Tony Cho
2015-09-11 7:53 ` [PATCH 7/7] staging: wilc1000: remove unused variables Tony Cho
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=55F8C3B0.8000902@atmel.com \
--to=tony.cho@atmel.com \
--cc=Nicolas.FERRE@atmel.com \
--cc=adel.noureldin@atmel.com \
--cc=adham.abozaeid@atmel.com \
--cc=austin.shin@atmel.com \
--cc=chris.park@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=glen.lee@atmel.com \
--cc=gregkh@linuxfoundation.org \
--cc=johnny.kim@atmel.com \
--cc=leo.kim@atmel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rachel.kim@atmel.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).