public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ian W MORRISON <ianwmorrison@gmail.com>
Cc: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Staging/IIO driver fixes for 4.12-rc1
Date: Sat, 6 May 2017 07:46:09 -0700	[thread overview]
Message-ID: <20170506144609.GA30980@kroah.com> (raw)
In-Reply-To: <01ddef41-93df-2bc3-0f3d-44c311dabb75@gmail.com>

On Sun, May 07, 2017 at 12:21:17AM +1000, Ian W MORRISON wrote:
> 
> On 5/6/17 11:41 PM, Greg KH wrote:
> > On Sat, May 06, 2017 at 06:00:24PM +1000, Ian W MORRISON wrote:
> > > The kernel when booted with Ubuntu 17.04 results in an unusable system
> > > however with the following patch booting is successful and the system
> > > is usable. The patch and kernel builds have been tested against on an
> > > Intel Compute Stick (STCK1A32WFC model).
> > It's in my queue to get to after 4.12-rc1 is out, it's not lost.
> > 
> > > <snip>
> > The patch is whitespace dammaged and can not be applied :(
> > 
> > thanks,
> > 
> > greg k-h
> 
> Here it is from a different email client. Hopefully preserving the
> whitespaces.
> 
> From: Ian W Morrison <linuxium@linuxium.com.au>
> Date: Fri, 28 Apr 2017 02:20:38 +1000
> Subject: [PATCH] staging: rtl8723bs: remove a call to kfree in
>  os_dep/ioctl_cfg80211.c
> 
> Signed-off-by: Ian W Morrison <linuxium@linuxium.com.au>
> ---
>  drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> b/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> index f17f4fb..2ee9df5 100644
> --- a/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> +++ b/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> @@ -3527,7 +3527,6 @@ int rtw_wdev_alloc(struct adapter *padapter, struct
> device *dev)
>          pwdev_priv->power_mgmt = true;
>      else
>          pwdev_priv->power_mgmt = false;
> -    kfree((u8 *)wdev);
> 
>      return ret;
> 

Still corrupted.

Let me go look at your original patch, we can take the thread there, as
this subject doesn't make sense :)

thanks,

greg k-h

      reply	other threads:[~2017-05-06 14:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 21:56 [GIT PULL] Staging/IIO driver fixes for 4.12-rc1 Greg KH
2017-05-05 21:57 ` [PATCH 1/3] staging: rtl8723bs: merge fix for add/change_virtual-intf API change Greg KH
2017-05-05 21:58   ` [PATCH 2/3] staging: rtl8723bs: merge fix for "nl80211: allow multiple active scheduled scan requests" Greg KH
2017-05-05 21:59     ` [PATCH 3/3] staging: rtl8723bs: fix up for cfg80211_roamed() API change Greg KH
2017-05-06 20:33       ` kbuild test robot
2017-05-06 20:28     ` [PATCH 2/3] staging: rtl8723bs: merge fix for "nl80211: allow multiple active scheduled scan requests" kbuild test robot
2017-05-06  8:00 ` [GIT PULL] Staging/IIO driver fixes for 4.12-rc1 Ian W MORRISON
2017-05-06 13:41   ` Greg KH
2017-05-06 14:21     ` Ian W MORRISON
2017-05-06 14:46       ` Greg KH [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=20170506144609.GA30980@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@linuxdriverproject.org \
    --cc=ianwmorrison@gmail.com \
    --cc=linux-kernel@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