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 F220CC433EF for ; Mon, 25 Jul 2022 13:54:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235187AbiGYNyK convert rfc822-to-8bit (ORCPT ); Mon, 25 Jul 2022 09:54:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38060 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234315AbiGYNyI (ORCPT ); Mon, 25 Jul 2022 09:54:08 -0400 Received: from mail-yb1-f172.google.com (mail-yb1-f172.google.com [209.85.219.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A1EA615802 for ; Mon, 25 Jul 2022 06:54:06 -0700 (PDT) Received: by mail-yb1-f172.google.com with SMTP id d124so2708437ybb.5 for ; Mon, 25 Jul 2022 06:54:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Ac81WFcClhe6PKs5MHDPcIypOaRXDUg/uSJ7/mPX0as=; b=ylC5Jt4QbQXQOJms5/M2leVxd9qvZJPalgzLt6hk+G532mNCkUslyDrDLvTvdeX2bO ud1TOL00XF+PkH2PC/F6Bxsriqzd+popDez8wbwalqgIfzaF8Xl/AtJIAKJUcMCo9NaR QUoqGqfUznTkR2G1Y1N7ErTQs8dnda5fw3uy7F9jzT8HJrl5juJIoccetjEPcZvTRRWX aYjOHQRZ2dq5Fd90JP6EYWO+bRrO2AnXxkvfrGfo9CZqFgZtYPmcj4M7cy7y2toIIiT2 M3c77pvMeCk+++gQ15eV5Yr5dchH27IAaWMovDrcxkj3wq183sE9oB6fDOPnDpRGTplO jBIw== X-Gm-Message-State: AJIora8aHJKEiU8I1r7cTh/JhCLSYEmsBs9a9IJ6VDzW5MBD3E8pzbZw JHV8T2L44HHxtEfQ5WqHgVJtnlnmrxVp1AdPwwYI3CK55wOKAg== X-Google-Smtp-Source: AGRyM1vfkeY+2sNWBGKwGVP7hredO5XrIUgro7IiA9rXKlkfozb5qjNIiPacAEm5mWk+33NBN/Bc2Iim/3d2sohBOe8= X-Received: by 2002:a25:946:0:b0:670:ccc5:774a with SMTP id u6-20020a250946000000b00670ccc5774amr8877682ybm.381.1658757245546; Mon, 25 Jul 2022 06:54:05 -0700 (PDT) MIME-Version: 1.0 References: <20220725133208.432176-1-mailhol.vincent@wanadoo.fr> In-Reply-To: <20220725133208.432176-1-mailhol.vincent@wanadoo.fr> From: Vincent MAILHOL Date: Mon, 25 Jul 2022 22:53:54 +0900 Message-ID: Subject: Re: [PATCH v1 00/24] can: add ethtool support and reporting of timestamping capabilities To: linux-can@vger.kernel.org, Marc Kleine-Budde Cc: Stephane Grosjean , Jimmy Assarsson , Oliver Hartkopp , Dario Binacchi , Max Staudt Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Precedence: bulk List-ID: X-Mailing-List: linux-can@vger.kernel.org On Sun. 25 Jul. 2022 at 22:32, Vincent Mailhol wrote: > This series revolves around ethtool and timestamping. Its ultimate > goal is that the timestamping implementation within socketCAN meets > the specification of other network drivers in the kernel. This way, > tcpdump or other tools derived from libpcap can be used to do > timestamping on CAN devices. For those of you who would like to test it, please have a look at the other series I just sent: https://lore.kernel.org/linux-can/20220725134345.432367-1-mailhol.vincent@wanadoo.fr/T/ @Marc, this is a long series (25 patches but many trivial ones) just one week before the merge windows. Overall, I have a good confidence on this series, except for the last four patches: can: kvaser_pciefd: advertise timestamping capabilities and add ioctl support can: kvaser_usb: advertise timestamping capabilities and add ioctl support can: peak_canfd: advertise timestamping capabilities and add ioctl support can: peak_usb: advertise timestamping capabilities and add ioctl support For those last four patches, I would like to get the feedback from Jimmy and Stéphane before it gets merged. If additional time is needed for testing, it might be wise to just merge the first 21 patches and leave those last 4 ones for the next cycle. Yours sincerely, Vincent Mailhol