Linux CAN drivers development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vivek Yadav <vivek.2311@samsung.com>,
	rcsekar@samsung.com, wg@grandegger.com, mkl@pengutronix.de,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, pankaj.dubey@samsung.com,
	ravi.patel@samsung.com, alim.akhtar@samsung.com
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Sriranjani P <sriranjani.p@samsung.com>
Subject: Re: [PATCH 3/7] arm64: dts: fsd: add sysreg device node
Date: Wed, 9 Nov 2022 12:13:55 +0100	[thread overview]
Message-ID: <21d373bc-c69b-866a-b6c2-58966f274eea@kernel.org> (raw)
In-Reply-To: <20221021095833.62406-4-vivek.2311@samsung.com>

On 21/10/2022 11:58, Vivek Yadav wrote:
> From: Sriranjani P <sriranjani.p@samsung.com>
> 
> Add SYSREG controller device node, which is available in PERIC and FSYS0
> block of FSD SoC.
> 
> Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
> Signed-off-by: Pankaj Kumar Dubey <pankaj.dubey@samsung.com>
> Signed-off-by: Sriranjani P <sriranjani.p@samsung.com>

You sent a v2 with correct CC list but I still would like to express
here my disappointment that you ignored kernel CC rules. You are pushing
SoC stuff bypassing SoC maintainers, so let's make it explicit for
Patchwork:

NAK.

Best regards,
Krzysztof


  reply	other threads:[~2022-11-09 11:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221021102614epcas5p18bcb932e697a378a8244bd91065c5496@epcas5p1.samsung.com>
2022-10-21  9:58 ` [PATCH 0/7] can: mcan: Add MCAN support for FSD SoC Vivek Yadav
2022-10-21  9:58   ` [PATCH 1/7] dt-bindings: Document the SYSREG specific compatibles found on " Vivek Yadav
2022-10-21  9:58   ` [PATCH 2/7] dt-bindings: can: mcan: Add ECC functionality to message ram Vivek Yadav
2022-10-25  7:24     ` Marc Kleine-Budde
2022-11-09  8:47       ` Vivek Yadav
2022-10-25  7:31     ` Marc Kleine-Budde
2022-11-09  8:52       ` Vivek Yadav
2022-10-21  9:58   ` [PATCH 3/7] arm64: dts: fsd: add sysreg device node Vivek Yadav
2022-11-09 11:13     ` Krzysztof Kozlowski [this message]
2022-10-21  9:58   ` [PATCH 4/7] can: mcan: enable peripheral clk to access mram Vivek Yadav
2022-10-25  7:44     ` Marc Kleine-Budde
2022-11-09  9:55       ` Vivek Yadav
2022-10-21  9:58   ` [PATCH 5/7] arm64: dts: fsd: Add MCAN device node Vivek Yadav
2022-10-25  7:44     ` Marc Kleine-Budde
2022-11-09  9:16       ` Vivek Yadav
2022-10-21  9:58   ` [PATCH 6/7] can: m_can: Add ECC functionality for message RAM Vivek Yadav
2022-10-25  8:16     ` Marc Kleine-Budde
2022-11-09  9:59       ` Vivek Yadav
2022-10-21  9:58   ` [PATCH 7/7] arm64: dts: fsd: Add support for error correction code " Vivek Yadav
2022-10-25  7:32   ` [PATCH 0/7] can: mcan: Add MCAN support for FSD SoC Marc Kleine-Budde
2022-11-09  8:55     ` Vivek Yadav

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=21d373bc-c69b-866a-b6c2-58966f274eea@kernel.org \
    --to=krzk@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pankaj.dubey@samsung.com \
    --cc=ravi.patel@samsung.com \
    --cc=rcsekar@samsung.com \
    --cc=sriranjani.p@samsung.com \
    --cc=vivek.2311@samsung.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