All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	devicetree@vger.kernel.org,
	Robert Marko <robert.marko@sartura.hr>,
	Luka Perkov <luka.perkov@sartura.hr>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Michael Walle <michael@walle.cc>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/5] dt-bindings: eeprom: Inherit from nvmem.yaml
Date: Mon, 14 Nov 2022 13:21:35 +0100	[thread overview]
Message-ID: <CAMRc=MetoyeD3neFo1yg128NYgDEAfvji+1FqNEym6BEHpFtOw@mail.gmail.com> (raw)
In-Reply-To: <20221114085659.847611-3-miquel.raynal@bootlin.com>

On Mon, Nov 14, 2022 at 9:57 AM Miquel Raynal <miquel.raynal@bootlin.com> wrote:
>
> EEPROMs can be nvmem providers. Let's make all EEPROM bindings
> reference nvmem.yaml as they should, so that nvmem cells and layout
> parsers can be safely described within the EEPROM nodes.
>
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---

Acked-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

  reply	other threads:[~2022-11-14 12:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14  8:56 [PATCH v4 0/5] Bindings for NVMEM layouts Miquel Raynal
2022-11-14  8:56 ` [PATCH v4 1/5] dt-bindings: nvmem: Introduce the nvmem-layout container Miquel Raynal
2022-11-16 20:52   ` Rob Herring
2022-11-14  8:56 ` [PATCH v4 2/5] dt-bindings: eeprom: Inherit from nvmem.yaml Miquel Raynal
2022-11-14 12:21   ` Bartosz Golaszewski [this message]
2022-11-16 20:52   ` Rob Herring
2022-11-14  8:56 ` [PATCH v4 3/5] dt-bindings: nvmem: add YAML schema for the sl28 vpd layout Miquel Raynal
2022-11-16 20:52   ` Rob Herring
2022-11-16 21:28     ` Miquel Raynal
2022-11-16 22:44       ` Srinivas Kandagatla
2022-11-14  8:56 ` [PATCH v4 4/5] dt-bindings: vendor-prefixes: Add ONIE Miquel Raynal
2022-11-14  8:56 ` [PATCH v4 5/5] dt-bindings: nvmem: add YAML schema for the ONIE tlv layout Miquel Raynal
2022-11-16 20:54   ` Rob Herring

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='CAMRc=MetoyeD3neFo1yg128NYgDEAfvji+1FqNEym6BEHpFtOw@mail.gmail.com' \
    --to=brgl@bgdev.pl \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luka.perkov@sartura.hr \
    --cc=michael@walle.cc \
    --cc=miquel.raynal@bootlin.com \
    --cc=robert.marko@sartura.hr \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.