From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH 0/1] staging: wilc1000: need feedback about a patch
Date: Mon, 17 Aug 2015 12:55:01 -0700 [thread overview]
Message-ID: <20150817195501.GA6591@kroah.com> (raw)
In-Reply-To: <cover.1439829770.git.raphael.beamonte@gmail.com>
On Mon, Aug 17, 2015 at 12:55:06PM -0400, Rapha?l Beamonte wrote:
> Hello there,
>
> I just started patching some drivers to familiarize myself better
> with the kernel and perhaps contribute more to it if I find things
> that I can actually handle! (hoping I'll be able to handle more and
> more throughout time).
>
> Doing so, I found out that in the wilc1000 (staging) driver, I got
> compiler warnings for casts from u32 variables to pointers and
> pointers to u32 variables.
This driver is known broken in this way, please see the many discussions
about this on the driverdevel mailing list as to what the original
developers of the code are trying to do to fix this, and attempts for
others who are also trying to clean it up in this way.
I'm also not going to take this type of changes from anyone that does
not have the hardware to properly test it, do you have the hardware that
this driver controls?
thanks,
greg k-h
next prev parent reply other threads:[~2015-08-17 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 16:55 [PATCH 0/1] staging: wilc1000: need feedback about a patch Raphaël Beamonte
2015-08-17 16:55 ` [PATCH 1/1] staging: wilc1000: replace addresses variables type from u32 to size_t for x64 systems Raphaël Beamonte
[not found] ` <14628.1439831571@turing-police.cc.vt.edu>
2015-08-17 17:33 ` Raphaël Beamonte
2015-08-17 19:55 ` Greg Kroah-Hartman [this message]
2015-08-17 23:20 ` [PATCH 0/1] staging: wilc1000: need feedback about a patch Raphaël Beamonte
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=20150817195501.GA6591@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernelnewbies@lists.kernelnewbies.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.