From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Keiji Hayashibara <hayashibara.keiji@socionext.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Jassi Brar <jaswinder.singh@linaro.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Heiko Stuebner <heiko@sntech.de>,
linux-kernel@vger.kernel.org, Kevin Hilman <khilman@baylibre.com>,
linux-rockchip@lists.infradead.org,
Joachim Eastwood <manabian@gmail.com>,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-amlogic@lists.infradead.org, Chen-Yu Tsai <wens@csie.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Carlo Caione <carlo@caione.org>
Subject: [PATCH 0/5] nvmem: some cleanups and sparse warning fixes
Date: Mon, 11 Sep 2017 22:00:59 +0900 [thread overview]
Message-ID: <1505134864-11975-1-git-send-email-yamada.masahiro@socionext.com> (raw)
Socionext is trying to add a new nvmem driver.
Before adding a new one, I'd like to be sure about the preferred
coding style in this subsystem, and build-up cleaner code base.
Please pick up what you like. Please feel free to throw away
what you do not like.
1/5, 2/5: convert kzalloc to stack because nvmem_config
is small one-time use data.
This is what we agreed in the discussion.
3/5, 4/5: fix sparse warning
For mtk-efuse, qfprom, the base address is the only private data
but, assigning (void __iomem *) to ->priv directly causes sparse
warnings.
5/5: clean-up of owner settings - if the owner field matches
nvmem->dev->driver->onwer, we need not set the onwer field
explicitly.
Masahiro Yamada (5):
nvmem: imx-iim: use stack for nvmem_config instead of malloc'ing it
nvmem: mtk-efuse: use stack for nvmem_config instead of malloc'ing it
nvmem: mtk-efuse: fix different address space warnings of sparse
nvmem: qfprom: fix different address space warnings of sparse
nvmem: set nvmem->owner to nvmem->dev->driver->owner if unset
drivers/nvmem/bcm-ocotp.c | 1 -
drivers/nvmem/core.c | 2 ++
drivers/nvmem/imx-iim.c | 24 +++++++++------------
drivers/nvmem/imx-ocotp.c | 1 -
drivers/nvmem/lpc18xx_eeprom.c | 1 -
drivers/nvmem/lpc18xx_otp.c | 1 -
drivers/nvmem/meson-efuse.c | 1 -
drivers/nvmem/mtk-efuse.c | 47 ++++++++++++++++++++++--------------------
drivers/nvmem/mxs-ocotp.c | 1 -
drivers/nvmem/qfprom.c | 27 +++++++++++++++---------
drivers/nvmem/rockchip-efuse.c | 1 -
drivers/nvmem/sunxi_sid.c | 1 -
drivers/nvmem/vf610-ocotp.c | 1 -
13 files changed, 54 insertions(+), 55 deletions(-)
--
2.7.4
next reply other threads:[~2017-09-11 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 13:00 Masahiro Yamada [this message]
2017-09-11 13:01 ` [PATCH 1/5] nvmem: imx-iim: use stack for nvmem_config instead of malloc'ing it Masahiro Yamada
2017-09-11 13:01 ` [PATCH 2/5] nvmem: mtk-efuse: " Masahiro Yamada
2017-09-20 16:32 ` Sean Wang
2017-09-21 2:09 ` Masahiro Yamada
2017-09-22 3:59 ` Sean Wang
2017-09-11 13:01 ` [PATCH 3/5] nvmem: mtk-efuse: fix different address space warnings of sparse Masahiro Yamada
2017-09-20 16:19 ` Sean Wang
2017-09-11 13:01 ` [PATCH 4/5] nvmem: qfprom: " Masahiro Yamada
2017-09-11 13:01 ` [PATCH 5/5] nvmem: set nvmem->owner to nvmem->dev->driver->owner if unset Masahiro Yamada
2017-09-20 10:02 ` [PATCH 0/5] nvmem: some cleanups and sparse warning fixes Masahiro Yamada
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=1505134864-11975-1-git-send-email-yamada.masahiro@socionext.com \
--to=yamada.masahiro@socionext.com \
--cc=carlo@caione.org \
--cc=hayashibara.keiji@socionext.com \
--cc=heiko@sntech.de \
--cc=jaswinder.singh@linaro.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=manabian@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=maxime.ripard@free-electrons.com \
--cc=mhiramat@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®