From: Greg KH <gregkh@linuxfoundation.org>
To: Jimmy Assarsson <jimmyassarsson@gmail.com>
Cc: Jimmy Assarsson <extja@kvaser.com>,
linux-can@vger.kernel.org, stable@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [PATCH] can: kvaser_usb: get CAN clock frequency from device
Date: Wed, 22 Dec 2021 13:00:05 +0100 [thread overview]
Message-ID: <YcMTRYM9J1mjeDh6@kroah.com> (raw)
In-Reply-To: <eaefb340-6677-1fcc-83c2-dacc17360b92@gmail.com>
On Wed, Dec 22, 2021 at 01:37:24AM +0100, Jimmy Assarsson wrote:
> Hi,
>
> I'm not familiar with the tag conventions used in the stable tree.
> This is a backport of upstream commit fb12797ab1fef480ad8a32a30984844444eeb00d,
> for stable 4.4, 4.9 and 4.14.
> How to properly specify this?
You just did!
Now all queued up, thanks.
greg k-h
prev parent reply other threads:[~2021-12-22 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 0:28 [PATCH] can: kvaser_usb: get CAN clock frequency from device Jimmy Assarsson
2021-12-22 0:37 ` Jimmy Assarsson
2021-12-22 12:00 ` 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=YcMTRYM9J1mjeDh6@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=extja@kvaser.com \
--cc=jimmyassarsson@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox