stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Jakub Kicinski <kuba@kernel.org>, Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	linux-can@vger.kernel.org, kernel@pengutronix.de,
	Chee Hou Ong <chee.houx.ong@intel.com>,
	Aman Kumar <aman.kumar@intel.com>,
	Pallavi Kumari <kumari.pallavi@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH net 1/2] Revert "can: m_can: pci: use custom bit timings for Elkhart Lake"
Date: Wed, 18 May 2022 15:47:10 +0300	[thread overview]
Message-ID: <2637cf42-b7da-a862-c599-ce418645629b@linux.intel.com> (raw)
In-Reply-To: <20220513102145.748db22c@kernel.org>

Hi

Sorry the late response. I was offline a few days.

On 5/13/22 20:21, Jakub Kicinski wrote:
>> Fixes: 0e8ffdf3b86d ("can: m_can: pci: use custom bit timings for Elkhart Lake")
>> Link: https://lore.kernel.org/all/20220512124144.536850-1-jarkko.nikula@linux.intel.com
>> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
>> Reported-by: Chee Hou Ong <chee.houx.ong@intel.com>
>> Reported-by: Aman Kumar <aman.kumar@intel.com>
>> Reported-by: Pallavi Kumari <kumari.pallavi@intel.com>
>> Cc: <stable@vger.kernel.org> # v5.16+
>> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> 
> nit: the hash in the fixes tag should be:
> 
> Fixes: ea4c1787685d ("can: m_can: pci: use custom bit timings for Elkhart Lake")
> 
> Do you want to respin or is the can tree non-rebasable?

Grr... Looks like I took accidentally linux-stable commit Id. Obviously 
too hurry to vacation :-|

Thanks for fixing it up Marc!

  parent reply	other threads:[~2022-05-18 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220513130819.386012-1-mkl@pengutronix.de>
2022-05-13 13:08 ` [PATCH net 1/2] Revert "can: m_can: pci: use custom bit timings for Elkhart Lake" Marc Kleine-Budde
2022-05-13 17:21   ` Jakub Kicinski
2022-05-14 19:00     ` Marc Kleine-Budde
2022-05-18 12:47     ` Jarkko Nikula [this message]
     [not found] <20220514185742.407230-1-mkl@pengutronix.de>
2022-05-14 18:57 ` Marc Kleine-Budde
2022-05-16  9:10   ` patchwork-bot+netdevbpf

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=2637cf42-b7da-a862-c599-ce418645629b@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=aman.kumar@intel.com \
    --cc=chee.houx.ong@intel.com \
    --cc=davem@davemloft.net \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=kumari.pallavi@intel.com \
    --cc=linux-can@vger.kernel.org \
    --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 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).