From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: alex.aring@gmail.com, miquel.raynal@bootlin.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, linux-wpan@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC net-next] net: mac802154: Remove unused ieee802154_mlme_tx_one
Date: Mon, 30 Dec 2024 17:44:48 +0000 [thread overview]
Message-ID: <Z3LcEIO8cRAHUUsG@gallifrey> (raw)
In-Reply-To: <173557391812.3760501.8550596228761441624.b4-ty@datenfreihafen.org>
* Stefan Schmidt (stefan@datenfreihafen.org) wrote:
> Hello linux@treblig.org.
>
> On Wed, 25 Dec 2024 01:24:23 +0000, linux@treblig.org wrote:
> > ieee802154_mlme_tx_one() was added in 2022 by
> > commit ddd9ee7cda12 ("net: mac802154: Introduce a synchronous API for MLME
> > commands") but has remained unused.
> >
> > Remove it.
> >
> > Note, there's still a ieee802154_mlme_tx_one_locked()
> > variant that is used.
> >
> > [...]
>
> Applied to wpan/wpan-next.git, thanks!
Thanks! I'd been thinking I had to wait for net-next to reopen.
Dave
> [1/1] net: mac802154: Remove unused ieee802154_mlme_tx_one
> https://git.kernel.org/wpan/wpan-next/c/bddfe23be8f8
>
> regards,
> Stefan Schmidt
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2024-12-30 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 1:24 [RFC net-next] net: mac802154: Remove unused ieee802154_mlme_tx_one linux
2024-12-30 9:05 ` Miquel Raynal
2024-12-30 15:53 ` Stefan Schmidt
2024-12-30 17:44 ` Dr. David Alan Gilbert [this message]
2024-12-30 18:00 ` Stefan Schmidt
2025-01-06 12:39 ` Dr. David Alan Gilbert
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=Z3LcEIO8cRAHUUsG@gallifrey \
--to=linux@treblig.org \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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.