mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Srinivas Neeli <srinivas.neeli@xilinx.com>
Cc: wg@grandegger.com, davem@davemloft.net, edumazet@google.com,
	appana.durga.rao@xilinx.com, sgoud@xilinx.com,
	michal.simek@xilinx.com, kuba@kernel.org, pabeni@redhat.com,
	linux-can@vger.kernel.org, netdev@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, git@xilinx.com
Subject: Re: [PATCH V2 1/2] Revert "can: xilinx_can: Limit CANFD brp to 2"
Date: Tue, 7 Jun 2022 11:09:06 +0200	[thread overview]
Message-ID: <20220607090906.pdkvr2pcflcvzq2e@pengutronix.de> (raw)
In-Reply-To: <20220607085654.4178-2-srinivas.neeli@xilinx.com>

[-- Attachment #1: Type: text/plain, Size: 695 bytes --]

On 07.06.2022 14:26:53, Srinivas Neeli wrote:
> This reverts commit 05ca14fdb6fe65614e0652d03e44b02748d25af7.
> 
> On early silicon engineering samples observed
> bit shrinking issue when we use brp as 1.
> Hence updated brp_min as 2. As in production
> silicon this issue is fixed,so reverting the patch.
> 
> Signed-off-by: Srinivas Neeli <srinivas.neeli@xilinx.com>

Should this be applied to -stable?

Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-06-07  9:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  8:56 [PATCH V2 0/2] xilinx_can: Update on xilinx can Srinivas Neeli
2022-06-07  8:56 ` [PATCH V2 1/2] Revert "can: xilinx_can: Limit CANFD brp to 2" Srinivas Neeli
2022-06-07  9:09   ` Marc Kleine-Budde [this message]
2022-06-07  8:56 ` [PATCH V2 2/2] can: xilinx_can: Add Transmitter delay compensation (TDC) feature support Srinivas Neeli
2022-06-07  9:19   ` Marc Kleine-Budde
2022-06-07  9:57     ` Vincent MAILHOL

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=20220607090906.pdkvr2pcflcvzq2e@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=appana.durga.rao@xilinx.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=git@xilinx.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sgoud@xilinx.com \
    --cc=srinivas.neeli@xilinx.com \
    --cc=wg@grandegger.com \
    /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

all inboxes | Powered by JetHome®