public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: spidev: Add compatible for LWE's btt device
Date: Wed, 26 Mar 2025 17:42:28 +0100	[thread overview]
Message-ID: <20250326174228.14dfdf8c@wsk> (raw)
In-Reply-To: <5661510e-3aea-4c07-88d6-2c3efccadb37@sirena.org.uk>

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

Hi Mark,

> On Fri, Feb 21, 2025 at 04:56:44PM +0100, Lukasz Majewski wrote:
> > The Liebherr's BTT devices are using spidev to communicate via
> > SPI to monitoring devices. Extend compatibles to allow proper
> > DTS description.  
> 
> This is fine but we need a bindings document update too
> (trivial-devices.yaml should be fine I think).

I've just resend the update for trival-devices.yaml.
https://lore.kernel.org/linux-devicetree/20250326140930.2587775-1-lukma@denx.de/T/#u

Hopefully you can pull it soon.

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

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

  reply	other threads:[~2025-03-26 16:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 15:56 [PATCH] spi: spidev: Add compatible for LWE's btt device Lukasz Majewski
2025-02-24 15:16 ` Mark Brown
2025-03-26 16:42   ` Lukasz Majewski [this message]
2025-03-26 16:55     ` Mark Brown
2025-03-26 17:24     ` [PATCH v2] " Lukasz Majewski
2025-03-26 17:34       ` Mark Brown
2025-03-26 17:45         ` Lukasz Majewski
2025-03-26 18:06           ` Mark Brown
2025-03-26 21:28             ` Lukasz Majewski

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=20250326174228.14dfdf8c@wsk \
    --to=lukma@denx.de \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@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