linux-kernel - Re: [PATCH] MFD maintainer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 19 Jun 2008 18:06:29 +0200
From:	"pHilipp Zabel" <philipp.zabel@...il.com>
To:	Dmitry <dbaryshkov@...il.com>
Cc:	ian <spyro@....com>, "Samuel Ortiz" <sameo@...nedhand.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Ben Dooks" <ben-linux@...ff.org>,
	"Russell King - ARM Linux" <linux@....linux.org.uk>
Subject: Re: [PATCH] MFD maintainer

On Thu, Jun 19, 2008 at 5:32 PM, Dmitry <dbaryshkov@...il.com> wrote:
> Hi,
>
> 2008/6/19 ian <spyro@....com>:
>> On Thu, 2008-06-19 at 15:12 +0400, Dmitry wrote:
>>
>>> > I'll tidy up the code and pop a branch on my git server for people to
>>> > review, if thats what people want.
>>>
>>> It's better to send patches to some ML.
>>
>> Well, the code I had is updated to match linus -git branch
>> eseries_release7 if anyones curious. (no real changes since last time
>> though)
>>
>>> > Dmitry - if you have any pending patches now is the time to send them on
>>> > over ;-)
>>>
>>> Actually the code I'm using has diverged a bit from the last code I've
>>> sent before this merging pulse.
>>
>> All progress is good :)
>>
>>> As you have seen, I've tried to submit parts of the core and tmio-nand
>>> driver as a start.
>>
>> Has any of that got merged yet? If so, I'll adapt my strategy to match
>> that, otherwise I'll try to keep all the drivers in parallel.
>>
>>>  Then I'd suggest to merge other tmio core bits (support for tc6387xb
>>>  and t7l66xb). The MMC, usb and fb cell drivers could benefit from
>>>  clocklib patches I'm trying to get in.
>>
>> I'd like to see those. I'll get MMC and USB updated ASAP.
>>
>> have you solved the clock-api-tied-to-platform-architecture problem ?
>
> There were plenty of tries to merge clocklib. Check lkml archives.

How could we stir up some interest in those patches again? The last
round didn't receive any comments.

regards
Philipp
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/