From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9F755C433EF for ; Mon, 25 Apr 2022 19:31:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244946AbiDYTet (ORCPT ); Mon, 25 Apr 2022 15:34:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54288 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230214AbiDYTes (ORCPT ); Mon, 25 Apr 2022 15:34:48 -0400 X-Greylist: delayed 340 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Mon, 25 Apr 2022 12:31:42 PDT Received: from proxima.lasnet.de (proxima.lasnet.de [78.47.171.185]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A1F6811097A; Mon, 25 Apr 2022 12:31:42 -0700 (PDT) Received: from [IPV6:2003:e9:d72c:58f3:5b3d:eb7c:dc29:a239] (p200300e9d72c58f35b3deb7cdc29a239.dip0.t-ipconnect.de [IPv6:2003:e9:d72c:58f3:5b3d:eb7c:dc29:a239]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: stefan@datenfreihafen.org) by proxima.lasnet.de (Postfix) with ESMTPSA id 23698C06A5; Mon, 25 Apr 2022 21:26:00 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=datenfreihafen.org; s=2021; t=1650914760; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jyVArQHkXYmLlgKSMojirf0oYGdy7SmtDrnAIXOWePY=; b=kGrLNYImeCGGhmpdOHqgtmcJXhSh71tgDKY8ysZ7Y3GoWF7fvyCTW858L+nSu90JmGn/n5 05LGyyR0bCminbK8XDlAX2ccfPJr6Nh1ePVZfQg8boS8BIPKlZV91YhbbsUYPLibOYM4bQ A156j1M5djkYlCpLqenc7Azz9Gz8RHXqJ4PYPskKcUmypIJ8rcut0pJjLgxeNF9u2dpJ0g H9IZXhjpF4+JhkFmqTceNOj5LiBB+xvurT2qKblUNKVb8vttB1OsnahpR8C0gRWekjIfyV kMvmTbsE4oK11mk5/qZPKLgAxFLDhQgFPqz1wBYJI3tSfPPJnGswA9N389DB4A== Message-ID: <02b35b0d-be2f-d4fb-433b-d34a4dbb6a92@datenfreihafen.org> Date: Mon, 25 Apr 2022 21:25:58 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: [PATCH v6 00/10] ieee802154: Better Tx error handling Content-Language: en-US To: Alexander Aring , Miquel Raynal Cc: linux-wpan - ML , "David S. Miller" , Jakub Kicinski , "open list:NETWORKING [GENERAL]" , David Girault , Romuald Despres , Frederic Blain , Nicolas Schodet , Thomas Petazzoni References: <20220407100903.1695973-1-miquel.raynal@bootlin.com> From: Stefan Schmidt In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hello. On 25.04.22 14:37, Alexander Aring wrote: > Hi, > > On Thu, Apr 7, 2022 at 6:09 AM Miquel Raynal 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 > > 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