From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: sayli karnik <karniksayli1995@gmail.com>,
outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] Doubt regarding use of a function
Date: Fri, 10 Mar 2017 22:28:20 +0100 [thread overview]
Message-ID: <20170310212820.GB11308@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1703101847510.3356@hadrien>
On Fri, Mar 10, 2017 at 06:50:22PM +0100, Julia Lawall wrote:
>
>
> On Fri, 10 Mar 2017, sayli karnik wrote:
>
> > On Fri, Mar 10, 2017 at 10:56 PM, Julia Lawall <julia.lawall@lip6.fr> wrote:
> > >
> > >
> > > On Fri, 10 Mar 2017, sayli karnik wrote:
> > >
> > >> ieee80211 has the following function which to me does nothing-
> > >> void ieee80211_tkip_null(void)
> > >> {
> > >> printk("============>%s()\n", __func__);
> >
> > This printk is commented..forgot the '//' before it
> >
> > >> return;
> > >> }
> > >>
> > >> Before its function call there is this comment-
> > >> /* These function were added to load crypte module autoly */
> > >> ieee80211_tkip_null();
> > >>
> > >> Is this function needed in the driver? If not, can I send in a patch
> > >> removing it?
> > >
> > > Are there any maintainers associated with the file? They would know
> > > better. I can't see that the function is doing anything useful.
> > >
> > maintainer.pl just displays Greg.
>
> Greg,
>
> Is there a general policy about:
>
> functions that do nothing
> code under comments
> boring logging message
>
> Can we assume that the code as it is in staging basically works, and while
> these things may have been a useful reminder in the past, now they can go?
Yes.
> Or is that too much to assume for a general rule?
Nope, delete away!
But note, this code does do something, so that functionality needs to be
preserved.
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-10 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 17:24 Doubt regarding use of a function sayli karnik
2017-03-10 17:26 ` [Outreachy kernel] " Julia Lawall
2017-03-10 17:35 ` sayli karnik
2017-03-10 17:50 ` Julia Lawall
2017-03-10 21:28 ` Greg Kroah-Hartman [this message]
2017-03-10 21:27 ` Greg KH
2017-03-11 6:44 ` sayli karnik
2017-03-11 7:02 ` 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=20170310212820.GB11308@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=karniksayli1995@gmail.com \
--cc=outreachy-kernel@googlegroups.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 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.