netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Stefan Schmidt <stefan@datenfreihafen.org>,
	linux-wpan - ML <linux-wpan@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
	David Girault <david.girault@qorvo.com>,
	Romuald Despres <romuald.despres@qorvo.com>,
	Frederic Blain <frederic.blain@qorvo.com>,
	Nicolas Schodet <nico@ni.fr.eu.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v6 00/10] ieee802154: Better Tx error handling
Date: Mon, 25 Apr 2022 08:37:07 -0400	[thread overview]
Message-ID: <CAB_54W4_oDrfNFLrRMnOBqE=yxTGh97OK94Fiip1FovbHNaKBQ@mail.gmail.com> (raw)
In-Reply-To: <20220407100903.1695973-1-miquel.raynal@bootlin.com>

Hi,

On Thu, Apr 7, 2022 at 6:09 AM Miquel Raynal <miquel.raynal@bootlin.com> wrote:
>
> The idea here is to provide a fully synchronous Tx API and also be able
> to be sure that a transfer has finished. This will be used later by
> another series. However, while working on this task, it appeared
> necessary to first rework the way MLME errors were (not) propagated to
> the upper layers. This small series tries to tackle exactly that, before
> introducing the synchronous API.
>

Acked-by: Alexander Aring <aahringo@redhat.com>

Thanks!

- Alex

  parent reply	other threads:[~2022-04-25 12:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 10:08 [PATCH v6 00/10] ieee802154: Better Tx error handling Miquel Raynal
2022-04-07 10:08 ` [PATCH v6 01/10] net: ieee802154: Enhance/fix the names of the MLME return codes Miquel Raynal
2022-04-07 10:08 ` [PATCH v6 02/10] net: ieee802154: Fill the list of " Miquel Raynal
2022-04-07 10:08 ` [PATCH v6 03/10] net: mac802154: Save a global error code on transmissions Miquel Raynal
2022-04-07 10:08 ` [PATCH v6 04/10] net: mac802154: Create an offloaded transmission error helper Miquel Raynal
2022-04-07 10:08 ` [PATCH v6 05/10] net: mac802154: Create an error helper for asynchronous offloading errors Miquel Raynal
2022-04-07 10:08 ` [PATCH v6 06/10] net: ieee802154: at86rf230: Call _xmit_hw_error() when failing to offload frames Miquel Raynal
2022-04-07 10:09 ` [PATCH v6 07/10] net: ieee802154: at86rf230: Forward Tx trac errors Miquel Raynal
2022-04-07 10:09 ` [PATCH v6 08/10] net: ieee802154: atusb: Call _xmit_hw_error() upon transmission error Miquel Raynal
2022-04-07 10:09 ` [PATCH v6 09/10] net: ieee802154: ca8210: Use core return codes instead of hardcoding them Miquel Raynal
2022-04-07 10:09 ` [PATCH v6 10/10] net: ieee802154: ca8210: Call _xmit_error() when a transmission fails Miquel Raynal
2022-04-25 12:37 ` Alexander Aring [this message]
2022-04-25 19:25   ` [PATCH v6 00/10] ieee802154: Better Tx error handling 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='CAB_54W4_oDrfNFLrRMnOBqE=yxTGh97OK94Fiip1FovbHNaKBQ@mail.gmail.com' \
    --to=alex.aring@gmail.com \
    --cc=davem@davemloft.net \
    --cc=david.girault@qorvo.com \
    --cc=frederic.blain@qorvo.com \
    --cc=kuba@kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=nico@ni.fr.eu.org \
    --cc=romuald.despres@qorvo.com \
    --cc=stefan@datenfreihafen.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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).