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 48129ECAAD1 for ; Tue, 30 Aug 2022 13:30:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230293AbiH3Nas (ORCPT ); Tue, 30 Aug 2022 09:30:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56320 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230292AbiH3Nao (ORCPT ); Tue, 30 Aug 2022 09:30:44 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D88F59E0D7 for ; Tue, 30 Aug 2022 06:30:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1661866240; 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: in-reply-to:in-reply-to:references:references; bh=C071C0Fu4zpnzqm2GxjZqFKUf2VQ3Uu+K+WnKl/q7NU=; b=IBDmdwXFM/V+JIyeI33OUXW7PkahaX50KQSHtI2CP4e6Ub5x+hfw2BVwosiRAcK95+7STm SSuALVL18huFHZ7TZtLcDdwK26l2ClIeTWKEWqM0FXOogsrQ0aMy9H5LD2MebKt/ZeaDZZ Nla5zk75gkZmsvxREQbBXGcA+tP2Lzw= Received: from mail-pj1-f69.google.com (mail-pj1-f69.google.com [209.85.216.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-391-NbXGCAAoPgGnkCbRzQDClg-1; Tue, 30 Aug 2022 09:30:39 -0400 X-MC-Unique: NbXGCAAoPgGnkCbRzQDClg-1 Received: by mail-pj1-f69.google.com with SMTP id e22-20020a17090a9a9600b001fdaec2c73aso2503658pjp.7 for ; Tue, 30 Aug 2022 06:30:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=C071C0Fu4zpnzqm2GxjZqFKUf2VQ3Uu+K+WnKl/q7NU=; b=XK9MPuWddtdClBQAUoJqmZTo8KpNEBcFn04JOhxMkoHnz+I8WCaxGlSvgbUWQX1+FW ladiK8TXt9CFG0sF8E6AQOxba4JMGO8vCdijvPRmlu0EHQkRhw71ObFLAzdfQXxcfHQ9 fNpMGCXQHfoOJMRkHWUrCzZxEQecD6vvoUBtV5wYyJ0P78LmLvG8tnJuL4Emji2bsr3C qjPW3zgnyPeZ9rPWh4hwJpSrMhr57xQ3wQP31UK/J5+bUn2HmDYvcNZEFn8OSVb1qc6+ WlDdhnwEtUZVF/mzOSrzfmqCObT/REJf0lN8v6TL/Wiq2eli2fzjWmm5/5ALxgZsbUTE fNJA== X-Gm-Message-State: ACgBeo0ulNsl1fZoBiUWCjkfB9rnUNNF7Cd0Yix7eRZWrzJpUI3MwPhn 0guHYuJhOa4fJ+kr5sjdHyltf9gXLcmpkQxoc6vw8bAhcSzEge/hv6fvl9M88F0SVaZZp4A2iqq MKixBtoGz1KzS6/nJAoEtJvJQ/KrnyyKUX1ZFrjA4 X-Received: by 2002:a63:d10b:0:b0:41d:bd7d:7759 with SMTP id k11-20020a63d10b000000b0041dbd7d7759mr17929708pgg.196.1661866237897; Tue, 30 Aug 2022 06:30:37 -0700 (PDT) X-Google-Smtp-Source: AA6agR7CO92TZNx1/ZDyoq+lGXimNNYaqY6rNHmUopJlR2o2q6TOwVRYYUayx8+y1zHvUDGFjESrSTgnSoi2AHd+NLQ= X-Received: by 2002:a63:d10b:0:b0:41d:bd7d:7759 with SMTP id k11-20020a63d10b000000b0041dbd7d7759mr17929681pgg.196.1661866237660; Tue, 30 Aug 2022 06:30:37 -0700 (PDT) MIME-Version: 1.0 References: <20220721153625.1282007-1-benjamin.tissoires@redhat.com> <20220721153625.1282007-25-benjamin.tissoires@redhat.com> In-Reply-To: From: Benjamin Tissoires Date: Tue, 30 Aug 2022 15:30:26 +0200 Message-ID: Subject: Re: [PATCH bpf-next v7 24/24] Documentation: add HID-BPF docs To: Bagas Sanjaya Cc: Greg KH , Jiri Kosina , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , Song Liu , Yonghong Song , Kumar Kartikeya Dwivedi , John Fastabend , KP Singh , Shuah Khan , Dave Marchevsky , Joe Stringer , Jonathan Corbet , Tero Kristo , lkml , "open list:HID CORE LAYER" , Networking , bpf , "open list:KERNEL SELFTEST FRAMEWORK" , Linux Doc Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 25, 2022 at 4:53 AM Bagas Sanjaya wrote: > > On Thu, Jul 21, 2022 at 05:36:25PM +0200, Benjamin Tissoires wrote: > > +When (and why) to use HID-BPF > > +============================= > > + > > +We can enumerate several use cases for when using HID-BPF is better than > > +using a standard kernel driver fix: > > + > > Better say "There are several use cases when using HID-BPF is better > than standard kernel driver fix:" OK, included locally, and will send it in v10. > > > +When a BPF program needs to emit input events, it needs to talk HID, and rely > > +on the HID kernel processing to translate the HID data into input events. > > + > > talk to HID? Replaced with "it needs to talk with the HID protocol". > > Otherwise the documentation LGTM (no new warnings caused by the doc). Great, thanks a lot for the review :) Cheers, Benjamin > > -- > An old man doll... just what I always wanted! - Clara