From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 00/22] Verbatim device names and devm_nvmem_(un)register()
Date: Thu, 25 Jan 2018 09:17:21 +0000 [thread overview]
Message-ID: <61e56a69-5722-138e-481e-44473a79b388@linaro.org> (raw)
In-Reply-To: <CAMRc=Mct60LMcr-CGJue1dTK+XNwz=dmkm2arTGeN1czeN9JoA@mail.gmail.com>
On 24/01/18 11:13, Bartosz Golaszewski wrote:
>>
> Hi Srinivas,
>
> I don't see this series in next - is it going to miss this merge window?
>
Thanks for your patience.
In general, I pick stuff which are sent before rc5-rc6 and send it to
Greg KH for inclusion in char-misc tree.
These patches will be queued for next release cycle..
Thanks,
srini
> Thanks,
> Bartosz
next prev parent reply other threads:[~2018-01-25 9:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 20:00 [PATCH v3 00/22] Verbatim device names and devm_nvmem_(un)register() Andrey Smirnov
2018-01-03 20:00 ` [PATCH v3 01/22] nvmem: Document struct nvmem_config Andrey Smirnov
2018-02-28 18:34 ` Sean Wang
2018-03-08 18:22 ` Andrey Smirnov
2018-01-03 20:00 ` [PATCH v3 02/22] nvmem: core: Allow specifying device name verbatim Andrey Smirnov
2018-01-03 20:00 ` [PATCH v3 03/22] nvmem: Introduce devm_nvmem_(un)register() Andrey Smirnov
2018-01-03 20:00 ` [PATCH v3 04/22] nvmem: vf610-ocotp: Convert to use devm_nvmem_register() Andrey Smirnov
2018-01-03 20:00 ` [PATCH v3 05/22] nvmem: imx-ocotp: " Andrey Smirnov
2018-01-03 20:00 ` [PATCH v3 06/22] nvmem: uniphier-efuse: " Andrey Smirnov
2018-01-03 20:00 ` [PATCH v3 07/22] nvmem: snvs_lgpr: " Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 08/22] nvmem: rockchip-efuse: " Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 09/22] nvmem: qfprom: " Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 10/22] nvmem: mtk-efuse: " Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 11/22] nvmem: meson-mx-efuse: " Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 12/22] nvmem: meson-efuse: " Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 13/22] nvmem: lpc18xx_otp: " Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 14/22] nvmem: imx-iim: " Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 15/22] nvmem: bcm-ocotp: " Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 16/22] nvmem: meson-efuse: Do no gate COMPILE_TEST with MESON_SM Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 17/22] nvmem: snvs_lpgpr: Convert commas to semicolons Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 18/22] nvmem: rockchip-efuse: Make use of of_device_get_match_data() Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 19/22] nvmem: vf610-ocotp: Do not use "&pdev->dev" explicitly Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 20/22] nvmem: rockchip-efuse: " Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 21/22] nvmem: imx-iim: " Andrey Smirnov
2018-01-03 20:01 ` [PATCH v3 22/22] nvmem: bcm-ocotp: " Andrey Smirnov
2018-01-24 11:13 ` [PATCH v3 00/22] Verbatim device names and devm_nvmem_(un)register() Bartosz Golaszewski
2018-01-25 9:17 ` Srinivas Kandagatla [this message]
2018-02-26 3:45 ` Andrey Smirnov
2018-02-26 9:30 ` 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=61e56a69-5722-138e-481e-44473a79b388@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).