linux-kernel - Re: [PATCH 1/2] soc: samsung: Change type of PMU configuration register value to u32

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]

Message-id: <5784AF35.9080302@samsung.com>
Date:	Tue, 12 Jul 2016 10:49:57 +0200
From:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
To:	Abhilash Kesavan <kesavan.abhilash@...il.com>
Cc:	linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	Kukjin Kim <kgene.kim@...sung.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] soc: samsung: Change type of PMU configuration
 register value to u32

On 07/11/2016 04:44 PM, Abhilash Kesavan wrote:
> Hi Krzysztof,
> 
> On Wed, Jul 6, 2016 at 8:47 AM, Krzysztof Kozlowski
> <k.kozlowski@...sung.com> wrote:
>> On Tue, Jul 5, 2016 at 10:28 PM, Abhilash Kesavan <a.kesavan@...sung.com> wrote:
>>> Exynos7 has certain PMU registers that needs to be configured with
>>> u32 values.
>>>
>>> Signed-off-by: Abhilash Kesavan <a.kesavan@...sung.com>
>>> ---
>>>  drivers/soc/samsung/exynos-pmu.h | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/soc/samsung/exynos-pmu.h b/drivers/soc/samsung/exynos-pmu.h
>>> index a469e36..1bdc506 100644
>>> --- a/drivers/soc/samsung/exynos-pmu.h
>>> +++ b/drivers/soc/samsung/exynos-pmu.h
>>> @@ -18,7 +18,7 @@
>>>
>>>  struct exynos_pmu_conf {
>>>         unsigned int offset;
>>> -       u8 val[NUM_SYS_POWERDOWN];
>>> +       unsigned int val[NUM_SYS_POWERDOWN];
>>
>> You mentioned u32 but I see unsigned int here. This should be u32.
> Will change.
>>
>> BTW, none of your emails reached my samsung inbox. I got them only
>> from the lists. Please investigate why this couldn't be delivered to
>> samsung.com address.
> 
> Not quite sure why that happened even after I added you as a
> recipient. I'll be posting some patches soon, let's see if the same
> occurs again or if it was a one-off case.

No problem with these mails so either this was one time issue or it was
caused by git-send-email and company's SMTP server.

Best regards,
Krzysztof