mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: marcus.wolf@smarthome-wolf.de
To: Valentin.Vidic@CARNet.hr, dan.carpenter@oracle.com
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	robsonde@gmail.com, michael.panzlaff@fau.de, hle@owl.eu.com,
	luca@acul.me, linux-kernel@vger.kernel.org,
	marcin.s.ciupak@gmail.com, linux@Wolf-Entwicklungen.de,
	simon@nikanor.nu, joe@perches.com
Subject: Re: [PATCH v3] staging: pi433: replace simple switch statements
Date: Mon, 25 Jun 2018 15:27:58 +0200 (CEST)	[thread overview]
Message-ID: <20180625132758.D724A2CE0120@dd39320.kasserver.com> (raw)
In-Reply-To: <20180625123554.dlpgejqmjm7haak4@mwanda>

Hi Dan,

I'd like to mention once more, that the idea of the abstraction was to 
support multiple modules of Hope-RF.
If the decision of the "team" of developer of this driver is, that it 
should be reduced to a Pi433 or RFM69CW driver only, I fully agree, 
that the abstraction layer isn't necessary (tough improving readability).

But if the "team" wants to extend the driver - here I explicitly want to 
Name Marcin Ciupak and Hogo Lefeuvre, both were discussing this with me - 
I highly recommend to keep the abstraction layer.

And once again, I have to announce, that - if noone appears, who wants to 
help me with selling Pi433 - I can't effort to let Pi433 on the market 
longer then end of this year. From this Point of view on long term it 
might be senseless to prepare a Pi433-only driver.

Cheers,
Marcus

Dan Carpenter schrieb am 25.06.2018 14:35:
> I'd still prefer if we just removed this abstraction entirely and used
> OPMODE_MODE_TRANSMIT everywhere instead of bringing "transmit" into it.
> 
> I know that every author thinks their abstraction will definitely be
> useful in the future, but generally kernel style is to remove
> abstractions.
> 
> But I guess this code is an improvement over the original so the patch
> is fine.
> 
> regards,
> dan carpenter
> 
>


  reply	other threads:[~2018-06-25 13:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-24  9:42 [PATCH] " Valentin Vidic
2018-06-24 15:26 ` Joe Perches
2018-06-24 16:25   ` [PATCH v2] " Valentin Vidic
2018-06-24 16:31     ` [PATCH v3] " Valentin Vidic
2018-06-25 11:09       ` marcus.wolf
2018-06-25 12:35       ` Dan Carpenter
2018-06-25 13:27         ` marcus.wolf [this message]
2018-06-25 13:43           ` Dan Carpenter

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=20180625132758.D724A2CE0120@dd39320.kasserver.com \
    --to=marcus.wolf@smarthome-wolf.de \
    --cc=Valentin.Vidic@CARNet.hr \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hle@owl.eu.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@Wolf-Entwicklungen.de \
    --cc=luca@acul.me \
    --cc=marcin.s.ciupak@gmail.com \
    --cc=michael.panzlaff@fau.de \
    --cc=robsonde@gmail.com \
    --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 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®