From: Greg KH <greg@kroah.com>
To: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-can@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH 5.15 0/3] m_can_pci bit timings for Elkhart Lake
Date: Mon, 20 Dec 2021 12:02:39 +0100 [thread overview]
Message-ID: <YcBiz/hxgxktWb2E@kroah.com> (raw)
In-Reply-To: <cover.1639990483.git.matthias.schiffer@ew.tq-group.com>
On Mon, Dec 20, 2021 at 10:22:14AM +0100, Matthias Schiffer wrote:
> The automated backport of "can: m_can: pci: use custom bit timings for
> Elkhart Lake" failed because I neglected to add Fixes tags to the other
> two patches it depends on.
>
> Matthias Schiffer (3):
> Revert "can: m_can: remove support for custom bit timing"
> can: m_can: make custom bittiming fields const
> can: m_can: pci: use custom bit timings for Elkhart Lake
>
> drivers/net/can/m_can/m_can.c | 24 ++++++++++++----
> drivers/net/can/m_can/m_can.h | 3 ++
> drivers/net/can/m_can/m_can_pci.c | 48 ++++++++++++++++++++++++++++---
> 3 files changed, 65 insertions(+), 10 deletions(-)
>
> --
> 2.25.1
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2021-12-20 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 9:22 [PATCH 5.15 0/3] m_can_pci bit timings for Elkhart Lake Matthias Schiffer
2021-12-20 9:22 ` [PATCH 5.15 1/3] Revert "can: m_can: remove support for custom bit timing" Matthias Schiffer
2021-12-20 9:22 ` [PATCH 5.15 2/3] can: m_can: make custom bittiming fields const Matthias Schiffer
2021-12-20 9:22 ` [PATCH 5.15 3/3] can: m_can: pci: use custom bit timings for Elkhart Lake Matthias Schiffer
2021-12-20 11:02 ` Greg KH [this message]
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=YcBiz/hxgxktWb2E@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.