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: <20151020082047.GA923@samsunx.samsung>
Date:	Tue, 20 Oct 2015 17:20:47 +0900
From:	Andi Shyti <andi.shyti@...sung.com>
To:	Pavel Fedin <p.fedin@...sung.com>
Cc:	'Krzysztof Kozlowski' <k.kozlowski@...sung.com>,
	'Pankaj Dubey' <pankaj.dubey@...sung.com>,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, kgene.kim@...sung.com,
	thomas.ab@...sung.com
Subject: Re: [PATCH v4 6/8] drivers: soc: add support for exynos SROM driver

Hi Pavel,

> > AFAIR Fedin was talking about missing functionality, not about adding
> > the contribution by himself. So he might add it or he might not. I did
> > not receive any commitments from him.
> 
>  I am waiting for the driver to be integrated, because i see it's constantly redesigned. Then i'll post my patches. By the way, they
> will be useful only if pin controller driver for 5410 is accepted upstream, several authors have done it but i still didn't see it
> in upstream.
>  Pin controller is needed in order to configure multi-functional pins correctly.
> 
> > The driver should be "proper" for
> > the time being (which could mean !PM dependency). If there is a need,
> > then the dependency will be removed.
> 
>  I can do it later if you prefer.

can we add the "depends on ... && PM" now, later, once
you'll extend it, you remove it again?

Personally I'd prefer this way rather than having a driver that 
does nothing in case of !PM.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ