linux-kernel - Re: [PATCH v7 2/2] mfd: syscon: Add non-DT support

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <5140CBB0.3000204@wwwdotorg.org>
Date:	Wed, 13 Mar 2013 12:55:44 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Alexander Shiyan <shc_work@...l.ru>
CC:	linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
	Dong Aisheng <dong.aisheng@...aro.org>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Thierry Reding <thierry.reding@...onic-design.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v7 2/2] mfd: syscon: Add non-DT support

On 03/13/2013 12:43 PM, Alexander Shiyan wrote:
>> On 03/13/2013 11:34 AM, Alexander Shiyan wrote:
>>> This patch allow using syscon driver from the platform data, i.e.
>>> possibility using driver on systems without oftree support.
>>> For search syscon device from the client drivers,
>>> "syscon_regmap_lookup_by_pdevname" function was added.
>>
>> This patch also removes the driver's remove() function, which isn't
>> mentioned in the commit description.
> 
> Driver is using resource managed functions, remove() is not necessary.

Ah right, I see that conversion was made in this patch. It seems like it
should be mentioned in the commit description, but it's probably not a
big deal unless there is some other reason to repost this.

--
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/