From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] Mediatek EFUSE Support
Date: Thu, 21 Jan 2016 15:46:57 +0100 [thread overview]
Message-ID: <56A0EF61.5080500@gmail.com> (raw)
In-Reply-To: <56A0EBF0.2020703@linaro.org>
On 21/01/16 15:32, Srinivas Kandagatla wrote:
>
>
> On 21/01/16 09:33, Matthias Brugger wrote:
>>
>>
>> On 14/12/15 11:07, Srinivas Kandagatla wrote:
>>> Hi Andrew,
>>>
>>> On 14/12/15 04:27, Daniel Kurtz wrote:
>>>> Hi Srinivas,
>>>>
>>>> On Thu, Nov 19, 2015 at 6:46 PM, Andrew-CT Chen
>>>> <andrew-ct.chen@mediatek.com> wrote:
>>>>> This patch adds EFUSE support driver which is used by other drivers
>>>>> like thermal sensor and HDMI impedance.
>>>>>
>>>>> There are some efuses these fuses store things like calibration data,
>>>>> speed bins.. etc. Drivers like thermal sensor, HDMI impedance would
>>>>> read out this data for configuring the driver.
>>>>>
>>>>> Change in v2:
>>>>> 1. Rebase to 4.4-rc1
>>>>> 2. Modify the driver Makefile for more consistent with other drivers
>>>>> 3. Modify the compatible string to "mediatek,mt8173-efuse" and
>>>>> "mediatek,efuse"
>>>>
>>>> Do you still plan to queue this for v4.5?
>>>>
>>> Sorry guys, for the long delay in replying your pings, got busy with
>>> regular office stuff :-)
>>>
>>> Yes, It should go in v4.5, I did send request with my sign-off to Greg,
>>> he should take it via char-misc tree.
>>>
>>
>> I can't see this patches in the char-misc tree [1].
>> Can you please double check?
>
> Hi Matthias,
> Thanks for the patience. You should expect them to see after v4.5-rc1,
> that's when Greg said he would push the patches.
>
I'm a bit puzzled. Wouldn't that mean that they will get into mainline
for v4.6.
I just want to know if I can take patch 3/3 through my v4.5-next branch
(which eventually will be merged into v4.6-rc1) or if I have to wait.
Thanks,
Matthias
next prev parent reply other threads:[~2016-01-21 14:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 10:46 [PATCH v2 0/3] Mediatek EFUSE Support Andrew-CT Chen
2015-11-19 10:46 ` [PATCH v2 1/3] dt-bindings: add document of mediatek efuse driver Andrew-CT Chen
2015-11-20 15:40 ` Rob Herring
2015-11-19 10:46 ` [PATCH v2 2/3] nvmem: mediatek: Add Mediatek EFUSE driver Andrew-CT Chen
2015-12-08 4:52 ` Nicolas Boichat
2015-11-19 10:46 ` [PATCH v2 3/3] dts: arm64: Add EFUSE device node Andrew-CT Chen
2016-02-10 17:48 ` Matthias Brugger
2015-12-14 4:27 ` [PATCH v2 0/3] Mediatek EFUSE Support Daniel Kurtz
2015-12-14 10:07 ` Srinivas Kandagatla
2016-01-21 9:33 ` Matthias Brugger
2016-01-21 14:32 ` Srinivas Kandagatla
2016-01-21 14:46 ` Matthias Brugger [this message]
2016-01-21 14:49 ` Srinivas Kandagatla
2016-02-01 10:23 ` Matthias Brugger
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=56A0EF61.5080500@gmail.com \
--to=matthias.bgg@gmail.com \
--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).