From: Greg KH <gregkh@linuxfoundation•org>
To: Larry Finger <Larry.Finger@lwfinger•net>
Cc: Dan Carpenter <dan.carpenter@oracle•com>,
devel@driverdev•osuosl.org, netdev@vger•kernel.org
Subject: Re: [PATCH NEXT 1/5] staging: r8188eu: Fix sparse warnings in ioctl_linux.c
Date: Thu, 24 Oct 2013 15:51:53 +0100 [thread overview]
Message-ID: <20131024145153.GA23431@kroah.com> (raw)
In-Reply-To: <526932DD.2080602@lwfinger.net>
On Thu, Oct 24, 2013 at 09:46:53AM -0500, Larry Finger wrote:
> On 10/24/2013 05:10 AM, Dan Carpenter wrote:
> > I have looked at how this is called from ioctl_private_call() and it
> > seems like these are actual user pointers and the code is buggy. The
> > patch silences the warnings instead of fixing the bugs.
>
> Thanks for the review.
>
> Greg - please drop this one and take only 2-5. Do you want a resubmission?
I can just drop it. I'm way behind on patches due to the kernel summit
and LinuxCon, so it will be a week or so before I can catch up, sorry.
greg k-h
next prev parent reply other threads:[~2013-10-24 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 3:31 [PATCH 0/5 NEXT V2] staging: r8188eu: Fix sparse warnings Larry Finger
2013-10-24 3:31 ` [PATCH NEXT 1/5] staging: r8188eu: Fix sparse warnings in ioctl_linux.c Larry Finger
2013-10-24 10:10 ` Dan Carpenter
2013-10-24 14:46 ` Larry Finger
2013-10-24 14:51 ` Greg KH [this message]
2013-10-24 3:31 ` [PATCH NEXT 2/5] staging: r8188eu: Fix sparse warnings in rtw_ieee80211.c Larry Finger
2013-10-24 3:31 ` [PATCH NEXT 3/5] staging: r8188eu: Fix sparse warnings in rtl8188e.cmd.c Larry Finger
2013-10-24 3:31 ` [PATCH NEXT 4/5] staging: r8188eu: Fix sparse warnings in rtw_mlme_ext.c Larry Finger
2013-10-24 3:31 ` [PATCH NEXT 5/5] staging: r8188eu: Fix sparse warnings in rtl_p2p.c Larry Finger
2013-10-24 10:11 ` Dan Carpenter
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=20131024145153.GA23431@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=Larry.Finger@lwfinger$(echo .)net \
--cc=dan.carpenter@oracle$(echo .)com \
--cc=devel@driverdev$(echo .)osuosl.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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