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.4 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 DC4D9C4741F for ; Wed, 4 Nov 2020 15:08:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 86B212074B for ; Wed, 4 Nov 2020 15:08:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=hartkopp.net header.i=@hartkopp.net header.b="b0iH0hNF" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729981AbgKDPIj (ORCPT ); Wed, 4 Nov 2020 10:08:39 -0500 Received: from mo4-p01-ob.smtp.rzone.de ([85.215.255.50]:36670 "EHLO mo4-p01-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729263AbgKDPIh (ORCPT ); Wed, 4 Nov 2020 10:08:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1604502513; s=strato-dkim-0002; d=hartkopp.net; h=In-Reply-To:Date:Message-ID:From:References:Cc:To:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=LFNlSnRIMqT5BtljLlTRrG6haADq6Msx9PuYf8a0aBY=; b=b0iH0hNFj++mVF46BTtlT26ZcSUMzT0gp/eAWiCG+v+xSBWxWiZ/c/4b8u512NuSfe qA08AT2iqfW9IJxCVQ3qbcMVpXp8+/te+LJRDJfwdwvZwy3Y2t/OzDkV9BQhLGcFQrHm tm/YmO3ARS6EO5aXjcYtaL22lB0jovhnVkY1REY4QYOTgFP+QSDfZtDO8T1PRKPW3rjq 6YbSv3uEWzt8DW+awsgLidLIUdpfD6y028rvGjlmS57nx3hWlFh/j8c/Hku5sP/wQpBL wdaLG3+VcGdvYhDhv5TQ007Y66BYSrzsyIM+GrBsakmTSCYgBgAiIHymHwbXp1CF1n8+ EtWA== X-RZG-AUTH: ":P2MHfkW8eP4Mre39l357AZT/I7AY/7nT2yrDxb8mjG14FZxedJy6qgO1o3TMaFqTGVNiO8lopw==" X-RZG-CLASS-ID: mo00 Received: from [192.168.10.137] by smtp.strato.de (RZmta 47.3.0 DYNA|AUTH) with ESMTPSA id L010bewA4F8OJtl (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Wed, 4 Nov 2020 16:08:24 +0100 (CET) Subject: Re: [PATCH v3 0/4] Introduce optional DLC element for Classic CAN To: Marc Kleine-Budde , mailhol.vincent@wanadoo.fr Cc: linux-can@vger.kernel.org References: <20201029083218.41505-1-socketcan@hartkopp.net> <05f5257e-2ece-d9d4-2481-57b05b961d10@hartkopp.net> <08cf2c95-df53-9ecb-d84a-9d95239b4b04@pengutronix.de> From: Oliver Hartkopp Message-ID: Date: Wed, 4 Nov 2020 16:08:24 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-can@vger.kernel.org On 03.11.20 23:27, Marc Kleine-Budde wrote: > On 11/3/20 11:26 PM, Marc Kleine-Budde wrote: >> On 11/3/20 11:33 AM, Oliver Hartkopp wrote: >>> Hello Marc, >>> >>> I did some more testing with different CAN-USB adapters and feel pretty >>> comfortable on the below patch set now. >>> >>> Would you think this is something for can-next? >> >> Yes, this would go via > > ...net-next/master ok There are some patches in the current linux-can pull request that have an impact on renaming the get_dlc helpers. Therefore I would have to wait until net is merged to net-next. But the net-next window will still be open for a while ... Thanks, Oliver