From: Greg KH <gregkh@linuxfoundation.org>
To: Dean Lee <dean.lee@atmel.com>
Cc: devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org,
johnny.kim@atmel.com, chris.park@atmel.com, rachel.kim@atmel.com
Subject: Re: [PATCH 1/3] staging: wilc1000: rework include wilc_oswrapper.h
Date: Mon, 15 Jun 2015 23:03:55 -0700 [thread overview]
Message-ID: <20150616060355.GA27044@kroah.com> (raw)
In-Reply-To: <adf4906fecff029d52e8c8e0e1537dd7f9ef568c.1434432989.git.dean.lee@atmel.com>
On Tue, Jun 16, 2015 at 02:38:20PM +0900, Dean Lee wrote:
> rework line '#include "wilc_oswrapper.h"'
> it does not require after change own data type to common data type.
>
> Signed-off-by: Dean Lee <dean.lee@atmel.com>
These are nice, but why isn't anyone sending me patches to fix the build
warnings in the driver right now? That's preventing it from being
enabled in linux-next right now, please someone fix that...
next prev parent reply other threads:[~2015-06-16 6:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 5:38 [PATCH 1/3] staging: wilc1000: rework include wilc_oswrapper.h Dean Lee
2015-06-16 5:38 ` [PATCH 3/3] staging: wilc1000: delete unused files (wilc_oswrapper.h wilc_type.h) Dean Lee
2015-06-16 6:03 ` Greg KH [this message]
2015-06-16 6:28 ` [PATCH 2/3] staging: wilc1000: rework include wilc_type.h Dean Lee
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=20150616060355.GA27044@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris.park@atmel.com \
--cc=dean.lee@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=johnny.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).