From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] nvmem: new drivers for v4.5
Date: Mon, 1 Feb 2016 10:33:12 +0000 [thread overview]
Message-ID: <56AF3468.2020806@linaro.org> (raw)
In-Reply-To: <20160111183018.GA10243@kroah.com>
Hi Greg,
On 11/01/16 18:30, Greg KH wrote:
> On Mon, Jan 11, 2016 at 01:21:44PM +0000, Srinivas Kandagatla wrote:
>>
>>
>> On 07/12/15 10:56, Srinivas Kandagatla wrote:
>>> Hi Greg,
>>>
>>> Here are 2 new nvmem drivers which are in the mailing list for long time
>>> and are good to go for some testing and find its way to v4.5-rc*.
>>>
>>> Could you please take these patches via char-misc tree.
>> Hi Greg,
>>
>> I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear
>> in your char-misc tree/linux-next.
>>
>> Just wanted to know whats your plan on these patches?
>
> To wait until after 4.5-rc1 is out, sorry, my patch backlog got huge
> during Nov/Dec due to other external issues, I'll be digging out from
> them after 4.5-rc1 is out.
Am not sure if this was forgotten, just wanted know if you still have
plans to pick this series for any rc on 4.5?
thanks,
srini
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2016-02-01 10:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 10:56 [PATCH 0/4] nvmem: new drivers for v4.5 Srinivas Kandagatla
2015-12-07 10:57 ` [PATCH 1/4] DT: nvmem: Add NXP LPC18xx EEPROM memory binding documentation Srinivas Kandagatla
2015-12-07 10:57 ` [PATCH 2/4] nvmem: NXP LPC18xx EEPROM memory NVMEM driver Srinivas Kandagatla
2015-12-07 10:57 ` [PATCH 3/4] dt-bindings: add document of mediatek efuse driver Srinivas Kandagatla
2015-12-07 10:58 ` [PATCH 4/4] nvmem: mediatek: Add Mediatek EFUSE driver Srinivas Kandagatla
2016-01-11 13:21 ` [PATCH 0/4] nvmem: new drivers for v4.5 Srinivas Kandagatla
2016-01-11 18:30 ` Greg KH
2016-01-19 18:15 ` Daniel Kurtz
2016-02-01 10:33 ` Srinivas Kandagatla [this message]
2016-02-01 21:06 ` Greg KH
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=56AF3468.2020806@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).