Message ID | 20220407100903.1695973-1-miquel.raynal@bootlin.com (mailing list archive) |
---|---|
Headers | show |
Series | ieee802154: Better Tx error handling | expand |
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
Hello. On 25.04.22 14:37, Alexander Aring wrote: > 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! These patches have been applied to the wpan-next tree and will be part of the next pull request to net-next. Thanks! regards Stefan Schmidt