From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Aring <aahringo@redhat.com>
Cc: stefan@datenfreihafen.org, linux-wpan@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCHv2 wpan-next 0/2] mac802154: atomic_dec_and_test() fixes
Date: Mon, 13 Jun 2022 16:14:57 +0200 [thread overview]
Message-ID: <20220613161457.0a05cda0@xps-13> (raw)
In-Reply-To: <20220613043735.1039895-1-aahringo@redhat.com>
Hi Alex,
aahringo@redhat.com wrote on Mon, 13 Jun 2022 00:37:33 -0400:
> Hi,
>
> I was wondering why nothing worked anymore. I found it...
>
> changes since v2:
>
> - fix fixes tags in mac802154: util: fix release queue handling
> - add patch mac802154: fix atomic_dec_and_test checks got somehow
> confused 2 patch same issue
I've got initially confused with your patchset but yes indeed the API
works the opposite way compared to my gut understanding.
We bought hardware and I am currently setting up a real network to
hopefully track these regressions myself in the future.
For these two patches:
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
>
> Alexander Aring (2):
> mac802154: util: fix release queue handling
> mac802154: fix atomic_dec_and_test checks
>
> net/mac802154/tx.c | 4 ++--
> net/mac802154/util.c | 6 +++---
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
Thanks,
Miquèl
next prev parent reply other threads:[~2022-06-13 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 4:37 [PATCHv2 wpan-next 0/2] mac802154: atomic_dec_and_test() fixes Alexander Aring
2022-06-13 4:37 ` [PATCHv2 wpan-next 1/2] mac802154: util: fix release queue handling Alexander Aring
2022-06-13 4:37 ` [PATCHv2 wpan-next 2/2] mac802154: fix atomic_dec_and_test checks Alexander Aring
2022-06-13 14:14 ` Miquel Raynal [this message]
2022-06-15 2:53 ` [PATCHv2 wpan-next 0/2] mac802154: atomic_dec_and_test() fixes Alexander Aring
2022-06-15 7:25 ` Miquel Raynal
2022-06-15 9:08 ` Miquel Raynal
2022-06-14 8:32 ` Stefan Schmidt
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=20220613161457.0a05cda0@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=aahringo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).