Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp10477854ybi; Thu, 25 Jul 2019 00:00:49 -0700 (PDT) X-Google-Smtp-Source: APXvYqwg9vDzeKlOM89cpRxFBjt+2zhyOaBBSHXt6Dytw/OdpTRF//P3FuA7gSF/f6hYSgDWdkkE X-Received: by 2002:a63:904:: with SMTP id 4mr13851450pgj.19.1564038048961; Thu, 25 Jul 2019 00:00:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564038048; cv=none; d=google.com; s=arc-20160816; b=Jk0r7R7Sv9rHqbvrkaJ9vwOCEKfzitkUKLuEJkbICjWbgiJYavgVzRzQzh9tc68gz8 Di/eDR4ec8L+dpxyT0bcozrxl6W44Td13kx0atfBL1vplBaQBj1maeX12qXWtvjqrqHC mtw+dvFa9PWRylGiYKnbyzSj89sHv8M0aJCzahRewCEkwEPq71dq7dfgT9GomxIdOgbk C60eH1GUolrCDbKIFlSIZ8O8/hraucEww/H3Cu+RZh7SAFKZRIcYbBpiBjl84dEodPQ+ YlAJl2mlg36IjbIh0tsWP1A5Vqy5CmC10cXNxuZOYzwi8LXRpBvCxHITUxk40zn242Vh rBeA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=zWnkE82gqRAMNGClHA1zvWTUxNLyLHBq2mLAjFgXTF8=; b=jvKeOfS7yQhrCPgq0tSJfT9ZcUIT0UtlxEd0Nghj2YEyndCRKzGJWta3hctck62Bs2 L1euolHZ6u7tpFCdletDOw35mP8AXZG3GNJs3ccjiD8q1nekdG2TNPSJ3Z47yg1Z6LnZ RWLDUG5N7h9qHPWqIY9pwUQcOLRxwpofpVPcSMV2aQpa1VjWhWfOLe0yPS1f5n9bysRw Rl5L/yrA/lRQozxuQJzHYDRn6wfpW9drH50s0+ic1svEgvJ3g5WFHakZo+WeQRSctlUv L53qdEpqsbU2WNQ8oF33kJx2CHfYHkOOPSnCZJzhe0MyW/MMG+1YwYWzDGvhggq77GA/ pKZQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=dkdppeqf; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x18si14005992pjq.71.2019.07.25.00.00.33; Thu, 25 Jul 2019 00:00:48 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=dkdppeqf; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729473AbfGYG7Y (ORCPT + 99 others); Thu, 25 Jul 2019 02:59:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:33312 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726479AbfGYG7X (ORCPT ); Thu, 25 Jul 2019 02:59:23 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BA6F321871; Thu, 25 Jul 2019 06:59:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564037962; bh=Xe+l4V9Bz5H90pXUVpwpyR0kc4IDBDqSB1YjehgmLd0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=dkdppeqfpCvxrXpgyq8c6jN0etpzOcFD1xOh4TdEUvTsSGlmL0nS/basfBC3XVena nbn+s/Vh4tYb981X/z/W9B4h/prm0GY5ouAyBxDa8oby4ENnn1o+Bl9PWvys7wDyPa yAZVvdRF7jus2QiXi+/Z4KoB3BksOYVAiCNzbixA= Date: Thu, 25 Jul 2019 08:28:34 +0200 From: Greg KH To: Dan Murphy Cc: wg@grandegger.com, mkl@pengutronix.de, davem@davemloft.net, linux-can@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v12 1/5] can: m_can: Create a m_can platform framework Message-ID: <20190725062834.GC5647@kroah.com> References: <20190509161109.10499-1-dmurphy@ti.com> <93530d94-ec65-de82-448e-f2460dd39fb9@ti.com> <0f6c41c8-0071-ed3a-9e65-caf02a0fbefe@ti.com> <6fa79302-ad32-7f43-f9d5-af70aa789284@ti.com> <437b6371-8488-a0ff-fa68-d1fb5a81bb8b@ti.com> <20190724064754.GC22447@kroah.com> <443fe5e5-5e5c-f669-1f4b-565d9f3dd6c8@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <443fe5e5-5e5c-f669-1f4b-565d9f3dd6c8@ti.com> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 24, 2019 at 10:36:02AM -0500, Dan Murphy wrote: > Hello > > On 7/24/19 1:47 AM, Greg KH wrote: > > On Tue, Jul 23, 2019 at 10:14:14AM -0500, Dan Murphy wrote: > > > Hello > > > > > > On 7/10/19 7:08 AM, Dan Murphy wrote: > > > > Hello > > > > > > > > On 6/17/19 10:09 AM, Dan Murphy wrote: > > > > > Marc > > > > > > > > > > On 6/10/19 11:35 AM, Dan Murphy wrote: > > > > > > Bump > > > > > > > > > > > > On 6/6/19 8:16 AM, Dan Murphy wrote: > > > > > > > Marc > > > > > > > > > > > > > > Bump > > > > > > > > > > > > > > On 5/31/19 6:51 AM, Dan Murphy wrote: > > > > > > > > Marc > > > > > > > > > > > > > > > > On 5/15/19 3:54 PM, Dan Murphy wrote: > > > > > > > > > Marc > > > > > > > > > > > > > > > > > > On 5/9/19 11:11 AM, Dan Murphy wrote: > > > > > > > > > > Create a m_can platform framework that peripheral > > > > > > > > > > devices can register to and use common code and register sets. > > > > > > > > > > The peripheral devices may provide read/write and configuration > > > > > > > > > > support of the IP. > > > > > > > > > > > > > > > > > > > > Acked-by: Wolfgang Grandegger > > > > > > > > > > Signed-off-by: Dan Murphy > > > > > > > > > > --- > > > > > > > > > > > > > > > > > > > > v12 - Update the m_can_read/write functions to > > > > > > > > > > create a backtrace if the callback > > > > > > > > > > pointer is NULL. - https://lore.kernel.org/patchwork/patch/1052302/ > > > > > > > > > > > > > > > > > > > Is this able to be merged now? > > > > > > > > ping > > > > > Wondering if there is anything else we need to do? > > > > > > > > > > The part has officially shipped and we had hoped to have driver > > > > > support in Linux as part of the announcement. > > > > > > > > > Is this being sent in a PR for 5.3? > > > > > > > > Dan > > > > > > > Adding Greg to this thread as I have no idea what is going on with this. > > Why me? What am I supposed to do here? I see no patches at all to do > > anything with :( > > I am not sure who to email. The maintainer seems to be on hiatus or super > busy with other work. Who is the maintainer? > So I added you to see if you know how to handle this.? Wolfgang Acked it but > he said Marc needs to pull Then work with them, again, what can I do if I can't even see the patches here? > it in.? We have quite a few users of this patchset. I have been hosting the > patchset in a different tree. > > These users keep pinging us for upstream status and all we can do is point > them to the > > LKML to show we are continuing to pursue inclusion. > > https://lore.kernel.org/patchwork/project/lkml/list/?series=393454 Looks sane, work with the proper developers, good luck! greg k-h