From: Greg KH <gregkh@linuxfoundation.org>
To: mike dupuis <mike.dupuis.0@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] Staging: rtl8192u: remove ieee80211_ccmp_null()
Date: Sun, 4 Oct 2015 09:49:40 +0100 [thread overview]
Message-ID: <20151004084940.GB30827@kroah.com> (raw)
In-Reply-To: <1443906596-2956-1-git-send-email-mike.dupuis.0@gmail.com>
On Sat, Oct 03, 2015 at 01:09:56PM -0800, mike dupuis wrote:
> This is a patch to remove the function ieee80211_ccmp_null().
> This function does nothing and can therefore be safely removed.
>
> Signed-off-by: Mike Dupuis <mike.dupuis.0@gmail.com>
> ---
> drivers/staging/rtl8192u/ieee80211/ieee80211_module.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_module.c b/drivers/staging/rtl8192u/ieee80211/ieee80211_module.c
> index 61edd57..af22ee5 100644
> --- a/drivers/staging/rtl8192u/ieee80211/ieee80211_module.c
> +++ b/drivers/staging/rtl8192u/ieee80211/ieee80211_module.c
> @@ -175,9 +175,6 @@ struct net_device *alloc_ieee80211(int sizeof_priv)
> ieee->last_packet_time[i] = 0;
> }
>
> -/* These function were added to load crypte module autoly */
> - ieee80211_ccmp_null();
> -
You didn't remove the function, only the call to it.
And I think you just broke the "autoload" logic that these "call a null
function" function calls were trying to solve, which isn't good at all.
Have you verified that everything correctly auto-loads when the device
is plugged into the system?
thanks,
greg k-h
next prev parent reply other threads:[~2015-10-04 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 21:09 mike dupuis
2015-10-04 8:49 ` Greg KH [this message]
[not found] ` <CABTjXUT5E3oK1e8OxqTDc+1wmoHxMFV4SM8RmJE_FhtEmg48cw@mail.gmail.com>
2015-10-04 19:43 ` Greg KH
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=20151004084940.GB30827@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.dupuis.0@gmail.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
all inboxes | Powered by JetHome®