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 7A1D9C43334 for ; Wed, 8 Jun 2022 12:56:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239520AbiFHM4C (ORCPT ); Wed, 8 Jun 2022 08:56:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40126 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239510AbiFHMz6 (ORCPT ); Wed, 8 Jun 2022 08:55:58 -0400 Received: from mail.enpas.org (zhong.enpas.org [IPv6:2a03:4000:2:537::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id ADA4326AFD; Wed, 8 Jun 2022 05:55:54 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by mail.enpas.org (Postfix) with ESMTPSA id 18FEC100022; Wed, 8 Jun 2022 12:55:52 +0000 (UTC) Date: Wed, 8 Jun 2022 14:55:49 +0200 From: Max Staudt To: Marc Kleine-Budde Cc: Dario Binacchi , linux-kernel@vger.kernel.org, Amarula patchwork , michael@amarulasolutions.com, "David S. Miller" , Eric Dumazet , Greg Kroah-Hartman , Jakub Kicinski , Jiri Slaby , Paolo Abeni , Sebastian Andrzej Siewior , Vincent Mailhol , Wolfgang Grandegger , linux-can@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [RFC PATCH 00/13] can: slcan: extend supported features Message-ID: <20220608145549.67f0f831.max@enpas.org> In-Reply-To: <20220608071947.pwl4whyzqpyubzqn@pengutronix.de> References: <20220607094752.1029295-1-dario.binacchi@amarulasolutions.com> <20220608021537.04c45cf9.max@enpas.org> <20220608071947.pwl4whyzqpyubzqn@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 8 Jun 2022 09:19:47 +0200 Marc Kleine-Budde wrote: > On 08.06.2022 02:15:37, Max Staudt wrote: > > To speed up the slcan cleanup, may I suggest looking at can327? > > > > It started as a modification of slcan, and over the past few months, > > it has gone through several review rounds in upstreaming. In fact, a > > *ton* of things pointed out during reviews would apply 1:1 to slcan. > > > > What's more, there's legacy stuff that's no longer needed. No > > SLCAN_MAGIC, no slcan_devs, ... it's all gone in can327. May I > > suggest you have a look at it and bring slcan's boilerplate in line > > with it? > > +1 > > Most of Dario's series looks good. I suggest that we mainline this > first. If there's interest and energy the slcan driver can be reworked > to re-use the more modern concepts of the can327 driver. Agreed. It does look good, and I'm glad to see slcan get some love. Thanks Dario! Max