From: Greg KH <gregkh@linuxfoundation.org>
To: Gargi Sharma <gs051095@gmail.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
outreachy-kernel@googlegroups.com, oleg.drokin@intel.com,
andreas.dilger@intel.com, jsimmons@infradead.org
Subject: Re: [Outreachy kernel] [PATCH v2] staging: lustre: Replace typedef with struct
Date: Tue, 28 Feb 2017 09:18:40 +0100 [thread overview]
Message-ID: <20170228081840.GA1035@kroah.com> (raw)
In-Reply-To: <CAOCi2DEvajT69tumvzBPYQjBBOkVB49FO+paGJSGasY+BZSeyg@mail.gmail.com>
On Tue, Feb 28, 2017 at 01:20:59PM +0530, Gargi Sharma wrote:
> On Tue, Feb 28, 2017 at 12:36 PM, Julia Lawall <julia.lawall@lip6.fr> wrote:
> >
> >
> >
> > On Tue, 28 Feb 2017, Gargi Sharma wrote:
> >
> > > As per the Linux kernel coding style guidelines, using typedef for a
> > > structure type is not recommended. Hence, occurences of typedefs have
> > > been removed. To find the occurences of the structures grep was used
> > > and no uses were found.
> >
> > Actually, I'm not sure to understand.� No uses of the structures were
> > found at all?� If so, they should just be dropped.� Or are there uses, but
> > they already have the word "struct" in front of them?
>
> The first structure "ext_acl_xattr_entry" is used as one of the fields in the�
> other structure "ext_acl_xattr_header". I could not find any uses of the
> structure
> "ext_acl_xattr_header" inside the staging directory. Should I drop these two
> structures then?
I think so, we shouldn't keep around structures that are not actually
used.
Unless the Lustre maintainers are hiding something somewhere else that
uses these?
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-28 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 7:01 [PATCH v2] staging: lustre: Replace typedef with struct Gargi Sharma
2017-02-28 7:06 ` [Outreachy kernel] " Julia Lawall
2017-02-28 7:50 ` Gargi Sharma
2017-02-28 8:18 ` Greg KH [this message]
2017-03-02 10:47 ` Dilger, Andreas
2017-03-02 17:21 ` Gargi Sharma
2017-03-03 10:19 ` Dilger, Andreas
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=20170228081840.GA1035@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=gs051095@gmail.com \
--cc=jsimmons@infradead.org \
--cc=julia.lawall@lip6.fr \
--cc=oleg.drokin@intel.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.