devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Christian Eggers <ceggers@arri.de>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] dt-bindings: eeprom: at25: add  fujitsu,mb85rs256 compatible
Date: Wed, 26 Jun 2024 08:35:06 +0200	[thread overview]
Message-ID: <20240626063506.GA4324@francesco-nb> (raw)
In-Reply-To: <20240612092934.12282-1-francesco@dolcini.it>

Hello Rob,

On Wed, Jun 12, 2024 at 11:29:34AM +0200, Francesco Dolcini wrote:
> From: Francesco Dolcini <francesco.dolcini@toradex.com>
> 
> The fujitsu,mb85rs256 is a 256 Kbit SPI memory FRAM in the same family
> as the two existing fujitsu,mb85rs* compatibles and at25 compatible.
> 
> Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> ---
> No changes in the driver is required for this to be used, a device tree
> file using it will come in a later step. Sending to minimize work
> slowdown because of TI DT maintainer requirements on DT bindings, see
> https://lore.kernel.org/all/469be7c2-6865-40d4-bd06-15dc3a08b3e3@kernel.org/
> for more details.
> ---
>  Documentation/devicetree/bindings/eeprom/at25.yaml | 1 +

Are you going to pick this patch? From what I can see in the past
it was either you or gregkh to apply patches to this file, however
gregkh is not in cc: here.

Francesco


  parent reply	other threads:[~2024-06-26  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  9:29 [PATCH v1] dt-bindings: eeprom: at25: add fujitsu,mb85rs256 compatible Francesco Dolcini
2024-06-12  9:49 ` Krzysztof Kozlowski
2024-06-26  6:35 ` Francesco Dolcini [this message]
2024-07-31 14:35   ` Rob Herring (Arm)

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=20240626063506.GA4324@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=ceggers@arri.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=francesco.dolcini@toradex.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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).