linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "D. Jeff Dionne" <djeffdionne@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	devicetree@vger.kernel.org, linux-sh@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Kousik Sanagavarapu <five231003@gmail.com>
Subject: Re: [PATCH] sh: j2: drop incorrect SPI controller max frequency property
Date: Wed, 24 Apr 2024 09:24:58 +0200	[thread overview]
Message-ID: <830cc6e5-44e5-4088-97c6-49d7a7fa8b38@linaro.org> (raw)
In-Reply-To: <A9A1C6C4-2B40-4769-9C9D-3A4DB2C27C95@gmail.com>

On 24/04/2024 08:59, D. Jeff Dionne wrote:
> Adrian,
> 
> IMHO, this driver should go through the SH tree.  Thanks Rob, for testing the patch.

Of course it should go via SH tree, that's not the point here. I don't
want to take sh patches.

Best regards,
Krzysztof


  reply	other threads:[~2024-04-24  7:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22  6:42 [PATCH] sh: j2: drop incorrect SPI controller max frequency property Krzysztof Kozlowski
2024-03-30  4:44 ` Rob Landley
2024-04-24  6:48 ` Krzysztof Kozlowski
2024-04-24  6:59   ` D. Jeff Dionne
2024-04-24  7:24     ` Krzysztof Kozlowski [this message]
2024-04-24  7:08   ` John Paul Adrian Glaubitz
2024-04-24  7:25   ` Krzysztof Kozlowski
2024-04-29  8:16 ` John Paul Adrian Glaubitz
2024-04-29  8:50   ` Krzysztof Kozlowski
2024-05-02 10:28 ` John Paul Adrian Glaubitz

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=830cc6e5-44e5-4088-97c6-49d7a7fa8b38@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=dalias@libc.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djeffdionne@gmail.com \
    --cc=five231003@gmail.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /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).