From: Greg KH <gregkh@linuxfoundation.org>
To: Marcus Wolf <marcus.wolf@smarthome-wolf.de>
Cc: "Simon Sandström" <simon@nikanor.nu>,
devel@driverdev.osuosl.org, linux@Wolf-Entwicklungen.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] staging: pi433: Move enum option_on_off to pi433_if.h
Date: Thu, 7 Dec 2017 07:14:09 +0100 [thread overview]
Message-ID: <20171207061409.GA7545@kroah.com> (raw)
In-Reply-To: <39be3007-a0a6-01ba-aca7-856c8e6f1ed0@smarthome-wolf.de>
On Thu, Dec 07, 2017 at 12:24:34AM +0200, Marcus Wolf wrote:
>
>
> Am 06.12.2017 um 22:42 schrieb Simon Sandström:
> > The enum is now only used for ioctl, so move it pi433_if.h.
> >
> > Signed-off-by: Simon Sandström <simon@nikanor.nu>
> > ---
> > drivers/staging/pi433/pi433_if.h | 5 +++++
> > drivers/staging/pi433/rf69_enum.h | 5 -----
> > 2 files changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/staging/pi433/pi433_if.h b/drivers/staging/pi433/pi433_if.h
> > index bcfe29840889..c8697d144e2b 100644
> > --- a/drivers/staging/pi433/pi433_if.h
> > +++ b/drivers/staging/pi433/pi433_if.h
> > @@ -37,6 +37,11 @@
> > /*---------------------------------------------------------------------------*/
> > +enum option_on_off {
> > + OPTION_OFF,
> > + OPTION_ON
> > +};
> > +
> > /* IOCTL structs and commands */
> > /**
> > diff --git a/drivers/staging/pi433/rf69_enum.h b/drivers/staging/pi433/rf69_enum.h
> > index b0715b4eb6ac..4e64e38ae4ff 100644
> > --- a/drivers/staging/pi433/rf69_enum.h
> > +++ b/drivers/staging/pi433/rf69_enum.h
> > @@ -18,11 +18,6 @@
> > #ifndef RF69_ENUM_H
> > #define RF69_ENUM_H
> > -enum option_on_off {
> > - OPTION_OFF,
> > - OPTION_ON
> > -};
> > -
> > enum mode {
> > mode_sleep,
> > standby,
> >
>
> Hi Simon,
>
> sorry - I have one more question.
>
> Why do you want to get rid of the enum option_on_off in rf69_enum.h. I
> generated that file just to store the enums.
>
> Now we have one enum at an other place...
No need to have lots of .h files. This is just a simple driver, it
should only have 1 .h file at most (for anything needed by userspace).
So moving these all into one file is good.
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-07 6:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 20:42 [PATCH 0/6] staging: pi433: Minor cleanup and style fixes Simon Sandström
2017-12-06 20:42 ` [PATCH 1/6] staging: pi433: Split rf69_set_crc_enabled into two functions Simon Sandström
2017-12-07 14:38 ` Greg KH
2017-12-07 14:58 ` Simon Sandström
2017-12-07 16:52 ` Greg KH
2017-12-06 20:42 ` [PATCH 2/6] staging: pi433: Split rf69_set_sync_enabled " Simon Sandström
2017-12-06 20:42 ` [PATCH 3/6] staging: pi433: Remove enum data_mode Simon Sandström
2017-12-06 20:42 ` [PATCH 4/6] staging: pi433: Combine all rf69_set_amplifier_x() Simon Sandström
2017-12-06 20:42 ` [PATCH 5/6] staging: pi433: Move enum option_on_off to pi433_if.h Simon Sandström
2017-12-06 22:24 ` Marcus Wolf
2017-12-07 6:14 ` Greg KH [this message]
2017-12-06 20:42 ` [PATCH 6/6] staging: pi433: Remove SET_CHECKED usage from pi433_probe Simon Sandström
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=20171207061409.GA7545@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@Wolf-Entwicklungen.de \
--cc=marcus.wolf@smarthome-wolf.de \
--cc=simon@nikanor.nu \
/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.