From: Greg KH <greg@kroah.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Sasha Levin <sashal@kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
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
Date: Mon, 28 Jan 2019 17:12:09 +0100 [thread overview]
Message-ID: <20190128161209.GA29530@kroah.com> (raw)
In-Reply-To: <20190124072610.7n2wzwiexdtvvh5p@pengutronix.de>
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...
next prev parent reply other threads:[~2019-01-28 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 13:21 pull-request: can 2019-01-22 Marc Kleine-Budde
2019-01-22 13:21 ` [PATCH 1/4] can: dev: __can_get_echo_skb(): fix bogous check for non-existing skb by removing it Marc Kleine-Budde
2019-01-22 13:21 ` [PATCH 2/4] can: bcm: check timer values before ktime conversion Marc Kleine-Budde
[not found] ` <20190123225748.AF445218A1@mail.kernel.org>
2019-01-24 9:13 ` Oliver Hartkopp
2019-01-22 13:21 ` [PATCH 3/4] can: flexcan: fix 'passing zero to ERR_PTR()' warning Marc Kleine-Budde
2019-01-22 13:21 ` [PATCH 4/4] can: flexcan: fix NULL pointer exception during bringup Marc Kleine-Budde
2019-01-22 13:35 ` Uwe Kleine-König
[not found] ` <20190123225745.3D239218A2@mail.kernel.org>
2019-01-24 7:26 ` Uwe Kleine-König
2019-01-28 16:12 ` Greg KH [this message]
2019-01-25 5:52 ` pull-request: can 2019-01-22 David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190128161209.GA29530@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).