All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Stefan Schmidt <stefan@datenfreihafen.org>,
	Alexander Aring <alex.aring@gmail.com>
Cc: Gal Pressman <gal@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, Leon Romanovsky <leonro@nvidia.com>,
	linux-wpan@vger.kernel.org
Subject: Re: [PATCH net-next] net: ieee802154: Fix compilation error when CONFIG_IEEE802154_NL802154_EXPERIMENTAL is disabled
Date: Wed, 31 Aug 2022 14:09:47 -0700	[thread overview]
Message-ID: <20220831140947.7e8d06ee@kernel.org> (raw)
In-Reply-To: <36f09967-b211-ef48-7360-b6dedfda73e3@datenfreihafen.org>

On Wed, 31 Aug 2022 22:59:14 +0200 Stefan Schmidt wrote:
> I was swamped today and I am only now finding time to go through mail.
> 
> Given the problem these ifdef are raising I am ok with having these 
> commands exposed without them.
> 
> Our main reason for having this feature marked as experimental is that 
> it does not have much exposure and we fear that some of it needs rewrites.
> 
> If that really is going to happen we will simply treat the current 
> commands as reserved/burned and come up with other ones if needed. While 
> I hope this will not be needed it is a fair plan for mitigating this.

Thanks for the replies. I keep going back and forth in my head on
what's better - un-hiding or just using NL802154_CMD_SET_WPAN_PHY_NETNS + 1 
as the start of validation, since it's okay to break experimental commands.

Any preference?

  reply	other threads:[~2022-08-31 21:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 10:12 [PATCH net-next] net: ieee802154: Fix compilation error when CONFIG_IEEE802154_NL802154_EXPERIMENTAL is disabled Gal Pressman
2022-08-30 11:52 ` Sudip Mukherjee (Codethink)
2022-08-31  6:13 ` Jakub Kicinski
2022-08-31  6:20   ` Gal Pressman
2022-08-31  6:23     ` Leon Romanovsky
2022-08-31  6:31     ` Jakub Kicinski
2022-08-31 18:21       ` Jakub Kicinski
2022-08-31 19:21         ` Alexander Aring
2022-08-31 20:59         ` Stefan Schmidt
2022-08-31 21:09           ` Jakub Kicinski [this message]
2022-08-31 21:13             ` Stefan Schmidt
2022-09-01  6:38             ` Leon Romanovsky
2022-09-01 12:50               ` Alexander Aring
2022-09-01 13:05                 ` Leon Romanovsky
2022-09-01 20:23               ` Jakub Kicinski
2022-09-02  2:48                 ` Alexander Aring
2022-09-02  3:00                   ` Jakub Kicinski
2022-09-02 10:35                     ` Leon Romanovsky

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=20220831140947.7e8d06ee@kernel.org \
    --to=kuba@kernel.org \
    --cc=alex.aring@gmail.com \
    --cc=davem@davemloft.net \
    --cc=gal@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stefan@datenfreihafen.org \
    /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.