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 X-Spam-Level: X-Spam-Status: No, score=-5.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 91450C433ED for ; Thu, 13 May 2021 01:35:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 710D461353 for ; Thu, 13 May 2021 01:35:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232974AbhEMBgz (ORCPT ); Wed, 12 May 2021 21:36:55 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:32829 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232318AbhEMBgv (ORCPT ); Wed, 12 May 2021 21:36:51 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A23CE5C0066; Wed, 12 May 2021 21:35:40 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 12 May 2021 21:35:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=animalcreek.com; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=DpVUZkigS0YBcpQTAee6c+OCcYp kgSAchYFyPrT0G/I=; b=SJFqvRwXKaHVDrp6yAbs5aDuYPqR5dMZEZPNWhqHCNL bAp/P8hbLXXc6IaZOb2xy7dRFIepJJqymysEeBW3wB1Xg4ThHWx2abvyvYkMsrzC 5QqwqQHxeIlHwQCH0kwlFwRMMpBP0w5qD8UMMeTBxuOFYvog8m4PQKcn4FHTMrzz 7EZeZlZ40d8YQ4pPlzXLdf1mMAno9mnGPeqZ53ZFRzYhmdEHtK7XLYregQrj74NB thZuThM1IkHXX0/JQuIrLdKagNdh7Ve8KwM8tfDkboF2s49HaNAog6wkg+dWC6i6 3cIOeKwWunVWTt9t+6wj4Y+aF8hBB3ZGBCdt8yNAmYQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=DpVUZk igS0YBcpQTAee6c+OCcYpkgSAchYFyPrT0G/I=; b=OefKtoattdw537PpJdXfxG jwqYDSvbE9GmGzKaTQTuiuPs1OXiw+fjvIlGUmED1+GIAs/z9S1DIjZo1CfoVaHo bEFSiD2CXGXQUTVSrXJoVLyqI/vz+7/V4nROPpTSwzFkaMEZDR2Q3RP5yTEj3ACV SdDBYE0bJ7S8qfhxVVnsn4d8ogsQSyeB7afqx8JPA7ktTxoRQBY5NmKl59yDzJp5 xhVhbLkkZPHWfL/pir7LPTDOV5IWVXa87Y2g+sc1s92jhGT4AiI+eus0KNYMaX74 NZOIm4MDCbaMJUdROT5iyT4/EoXt+0cPzZO0LiYUPIROXY8Ra9OAH2xJIOK/aWLg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdehfedggeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjohesthdtredttddtvdenucfhrhhomhepofgrrhhk ucfirhgvvghruceomhhgrhgvvghrsegrnhhimhgrlhgtrhgvvghkrdgtohhmqeenucggtf frrghtthgvrhhnpedtheegudevteevkeeffeevudffvdejkeeitdekveeugfetleetheeg gfduhfdtieenucffohhmrghinhepqhhtrdhiohenucfkphepjedtrddujedvrdefvddrvd dukeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehm ghhrvggvrhesrghnihhmrghltghrvggvkhdrtghomh X-ME-Proxy: Received: from blue.animalcreek.com (ip70-172-32-218.ph.ph.cox.net [70.172.32.218]) by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 12 May 2021 21:35:39 -0400 (EDT) Received: by blue.animalcreek.com (Postfix, from userid 1000) id 431E4136008E; Wed, 12 May 2021 18:35:38 -0700 (MST) Date: Wed, 12 May 2021 18:35:38 -0700 From: Mark Greer To: Krzysztof Kozlowski Cc: Mark Greer , Frieder Schrempf , Jakub Kicinski , "David S. Miller" , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nfc@lists.01.org, Alex Blasche Subject: Re: [linux-nfc] [PATCH 1/2] MAINTAINERS: nfc: add Krzysztof Kozlowski as maintainer Message-ID: <20210513013538.GA239989@animalcreek.com> References: <20210512144319.30852-1-krzysztof.kozlowski@canonical.com> <14e78a9a-ed1a-9d7d-b854-db6d811f4622@kontron.de> <20210512170135.GB222094@animalcreek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Animal Creek Technologies, Inc. Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 12, 2021 at 04:21:25PM -0400, Krzysztof Kozlowski wrote: > On 12/05/2021 13:01, Mark Greer wrote: > > Re: QT - I've already talked to Alex Blasche from QT (CC'd). With some > > work we can get Linux NFC/neard back into their good graces. I/we need > > to find time to put in the work, though. > > > > An example of the issues they have seen is: > > > > https://bugreports.qt.io/browse/QTBUG-43802 > > > > Another issue I have--and I suspect you, Krzysztof, have as well--is > > lack of hardware. If anyone reading this wants to volunteer to be a > > tester, please speak up. > > Yes, testing would be very appreciated. I don't know how many unit tests > neard has, but maybe some mockups with unit testing would solve some of > problems? I'm not sure what you mean by this. Do you mean creating some tests that sit directly on top of the kernel and test the kernel parts (e.g., use netlink)? If so, that would be useful but you may end up implementing some of the NFC stack. If you mean more/better tests that use neard to exercise the whole stack then that would be really good too. Speaking of NFC stack, the NFC forum has their specs paywalled which is a real bummer/pain. I can try reaching out to them to see if they will help us help their mission but I'm not hopeful. FYI, most of the issues that I ran into and know still exist are timing/race issues in neard. I'm sure if we tested more, we could find some in the kernel though. Mark -- From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============7531734234054534802==" MIME-Version: 1.0 From: Mark Greer To: linux-nfc@lists.01.org Subject: [linux-nfc] Re: [PATCH 1/2] MAINTAINERS: nfc: add Krzysztof Kozlowski as maintainer Date: Wed, 12 May 2021 18:35:38 -0700 Message-ID: <20210513013538.GA239989@animalcreek.com> In-Reply-To: cd7a0110-702a-6e14-527e-fb4b53705870@canonical.com --===============7531734234054534802== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Wed, May 12, 2021@04:21:25PM -0400, Krzysztof Kozlowski wrote: > On 12/05/2021 13:01, Mark Greer wrote: > > Re: QT - I've already talked to Alex Blasche from QT (CC'd). With some > > work we can get Linux NFC/neard back into their good graces. I/we need > > to find time to put in the work, though. > > = > > An example of the issues they have seen is: > > = > > https://bugreports.qt.io/browse/QTBUG-43802 > > = > > Another issue I have--and I suspect you, Krzysztof, have as well--is > > lack of hardware. If anyone reading this wants to volunteer to be a > > tester, please speak up. > = > Yes, testing would be very appreciated. I don't know how many unit tests > neard has, but maybe some mockups with unit testing would solve some of > problems? I'm not sure what you mean by this. Do you mean creating some tests that sit directly on top of the kernel and test the kernel parts (e.g., use netlink)? If so, that would be useful but you may end up implementing some of the NFC stack. If you mean more/better tests that use neard to exercise the whole stack then that would be really good too. Speaking of NFC stack, the NFC forum has their specs paywalled which is a real bummer/pain. I can try reaching out to them to see if they will help us help their mission but I'm not hopeful. FYI, most of the issues that I ran into and know still exist are timing/race issues in neard. I'm sure if we tested more, we could find some in the kernel though. Mark -- --===============7531734234054534802==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============1974987224161881884==" MIME-Version: 1.0 From: Mark Greer To: linux-nfc@lists.01.org Subject: Re: [PATCH 1/2] MAINTAINERS: nfc: add Krzysztof Kozlowski as maintainer Date: Wed, 12 May 2021 18:35:38 -0700 Message-ID: <20210513013538.GA239989@animalcreek.com> In-Reply-To: List-Id: --===============1974987224161881884== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Wed, May 12, 2021 at 04:21:25PM -0400, Krzysztof Kozlowski wrote: > On 12/05/2021 13:01, Mark Greer wrote: > > Re: QT - I've already talked to Alex Blasche from QT (CC'd). With some > > work we can get Linux NFC/neard back into their good graces. I/we need > > to find time to put in the work, though. > > = > > An example of the issues they have seen is: > > = > > https://bugreports.qt.io/browse/QTBUG-43802 > > = > > Another issue I have--and I suspect you, Krzysztof, have as well--is > > lack of hardware. If anyone reading this wants to volunteer to be a > > tester, please speak up. > = > Yes, testing would be very appreciated. I don't know how many unit tests > neard has, but maybe some mockups with unit testing would solve some of > problems? I'm not sure what you mean by this. Do you mean creating some tests that sit directly on top of the kernel and test the kernel parts (e.g., use netlink)? If so, that would be useful but you may end up implementing some of the NFC stack. If you mean more/better tests that use neard to exercise the whole stack then that would be really good too. Speaking of NFC stack, the NFC forum has their specs paywalled which is a real bummer/pain. I can try reaching out to them to see if they will help us help their mission but I'm not hopeful. FYI, most of the issues that I ran into and know still exist are timing/race issues in neard. I'm sure if we tested more, we could find some in the kernel though. Mark -- --===============1974987224161881884==--