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=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham 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 D10DFC282CD for ; Mon, 28 Jan 2019 16:12:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A1EEF2175B for ; Mon, 28 Jan 2019 16:12:16 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=kroah.com header.i=@kroah.com header.b="dMnn369T"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="fWIXFFdR" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733101AbfA1QMP (ORCPT ); Mon, 28 Jan 2019 11:12:15 -0500 Received: from new1-smtp.messagingengine.com ([66.111.4.221]:59285 "EHLO new1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733111AbfA1QMO (ORCPT ); Mon, 28 Jan 2019 11:12:14 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id A9115C08C; Mon, 28 Jan 2019 11:12:12 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Mon, 28 Jan 2019 11:12:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:content-transfer-encoding:in-reply-to; s=fm2; bh=F Byyp/2jR/wF8Mz+Sq3mWd7mZDq/CchNJaYaaD6A8Yw=; b=dMnn369TzKYGVDHFy WdSuGfdumGwSzHoHyypw5/flq8zxiPEw2k2jkapBNckGVOjpisdyUIwyLcHNCoJ8 INgaEZLxCAu6mf32TEB+BO3b6ymHiDsyAh4kc91S5fsuGt+iqzofnlWIzKRRoTC1 4Edp9EyWMNCTPMOsr10WFl8batbXQYlx4gOM1tHjFjfGp6bNuqor2uh89dqtuPmA 7dkrU7kA3IBtGdJcQK5JnJR5YZPWwgp8oBJMDRurpL3NUh+L4yCBA9WG0GnPIKxz vmitov6W/b5EE7pAVw4C+xT7g449NZ3QI6qdTm6I7fk9L4+zp6gwtpN3SvcOqOBq S8/vg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=FByyp/2jR/wF8Mz+Sq3mWd7mZDq/CchNJaYaaD6A8 Yw=; b=fWIXFFdRaSHZsh/4w82JSO9coQXKxH2hxg2y55C68A0T1+QhV4Z6ionKX BysdMl9OzAItAl2YADE3qVzX8INDdDn8ujMzF1KAHZZfDjkvHWbto4LwmtdzaLqo IEoORHnb0EgxeZmb7hk3sCD+xCjhnZaX4D5/z4RKHsKQyFYV/MsGeGemFb2m7bnc Nu8Et6A48xvreP0gU8zepHuelb8lKB/ZyFB2RK5tpqcFoTntQ9HAJy7UkaxiVoyy 2Pqfa84hQQMuy8Ide/R4NqpILCNyLn2g9Od7ChXVaogkOAm6tXb+IzuxTPyUbzST nRRHIJE7UIP9fFYxp3LerAH588eWA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrjedtgdeklecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnegoufhprghmkfhpucdlfedttd dmnecujfgurhepfffhvffukfhfgggtugfgjggfsehtkeertddtredunecuhfhrohhmpefi rhgvghcumffjuceoghhrvghgsehkrhhorghhrdgtohhmqeenucfkphepkeefrdekiedrke elrddutdejnecurfgrrhgrmhepmhgrihhlfhhrohhmpehgrhgvgheskhhrohgrhhdrtgho mhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from localhost (5356596b.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id E10E1E432B; Mon, 28 Jan 2019 11:12:11 -0500 (EST) Date: Mon, 28 Jan 2019 17:12:09 +0100 From: Greg KH To: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= Cc: Sasha Levin , Marc Kleine-Budde , netdev@vger.kernel.org, davem@davemloft.net, linux-can@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 4/4] can: flexcan: fix NULL pointer exception during bringup Message-ID: <20190128161209.GA29530@kroah.com> References: <20190122132116.7074-5-mkl@pengutronix.de> <20190123225745.3D239218A2@mail.kernel.org> <20190124072610.7n2wzwiexdtvvh5p@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190124072610.7n2wzwiexdtvvh5p@pengutronix.de> User-Agent: Mutt/1.11.2 (2019-01-07) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, Jan 24, 2019 at 08:26:10AM +0100, Uwe Kleine-König wrote: > Hello Sasha, > > On Wed, Jan 23, 2019 at 10:57:44PM +0000, Sasha Levin wrote: > > [This is an automated email] > > Not sure if I only state the obvious that was just missed by your > automation. > > > > This commit has been processed because it contains a "Fixes:" tag, > > fixing commit: cbffaf7aa09e can: flexcan: Always use last mailbox for TX. > > > > The bot has tested the following trees: v4.20.3, v4.19.16. > > > > v4.20.3: Failed to apply! Possible dependencies: > > 0517961ccdf1 ("can: flexcan: Add provision for variable payload size") > > 22233f7bf2c9 ("can: flexcan: FLEXCAN_IFLAG_MB: add () around macro argument") > > 5156c7b11f35 ("can: flexcan: move rx_offload_add() from flexcan_probe() to flexcan_open()") > > 7ad0f53a394b ("can: flexcan: flexcan_chip_start(): enable loopback mode in flexcan") > > de3578c198c6 ("can: flexcan: add self wakeup support") > > > > v4.19.16: Failed to apply! Possible dependencies: > > 0517961ccdf1 ("can: flexcan: Add provision for variable payload size") > > 22233f7bf2c9 ("can: flexcan: FLEXCAN_IFLAG_MB: add () around macro argument") > > 5156c7b11f35 ("can: flexcan: move rx_offload_add() from flexcan_probe() to flexcan_open()") > > 7ad0f53a394b ("can: flexcan: flexcan_chip_start(): enable loopback mode in flexcan") > > de3578c198c6 ("can: flexcan: add self wakeup support") > > > > > > How should we proceed with this patch? > > When I posted the commit I also posted one that fits on top of v4.19.x. > I would expect that the same also fits on v4.20.x. If not, tell me. Ah, I see that now, sorry for the noise of the FAILED email...