All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: [PATCH 0/4] nvmem: patches (set 3) for 5.18
Date: Fri, 25 Feb 2022 17:58:18 +0000	[thread overview]
Message-ID: <20220225175822.8293-1-srinivas.kandagatla@linaro.org> (raw)

Hi Greg,

Here is set of nvmem patches for 5.18 which includes

- A fix for dt_bindings check failure on Sunplus nvmem bindings.
- update to nvmem bindings
- Parse cells from pre-encoded info in brcm nvmem provider.

Can you please queue them up for 5.18.

Thanks,
srini

Rafał Miłecki (3):
  nvmem: brcm_nvram: parse NVRAM content into NVMEM cells
  dt-bindings: nvmem: make "reg" property optional
  dt-bindings: nvmem: brcm,nvram: add basic NVMEM cells

Vincent Shih (1):
  nvmem: dt-bindings: Fix the error of dt-bindings check

 .../devicetree/bindings/nvmem/brcm,nvram.yaml | 25 +++++-
 .../devicetree/bindings/nvmem/nvmem.yaml      |  3 -
 .../bindings/nvmem/sunplus,sp7021-ocotp.yaml  |  4 +-
 drivers/nvmem/brcm_nvram.c                    | 90 +++++++++++++++++++
 4 files changed, 114 insertions(+), 8 deletions(-)

-- 
2.21.0


             reply	other threads:[~2022-02-25 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 17:58 Srinivas Kandagatla [this message]
2022-02-25 17:58 ` [PATCH 1/4] nvmem: dt-bindings: Fix the error of dt-bindings check Srinivas Kandagatla
2022-02-25 17:58 ` [PATCH 2/4] nvmem: brcm_nvram: parse NVRAM content into NVMEM cells Srinivas Kandagatla
2022-02-25 17:58 ` [PATCH 3/4] dt-bindings: nvmem: make "reg" property optional Srinivas Kandagatla
2022-02-25 17:58 ` [PATCH 4/4] dt-bindings: nvmem: brcm,nvram: add basic NVMEM cells Srinivas Kandagatla

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=20220225175822.8293-1-srinivas.kandagatla@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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 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.