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: <a3d7c16f-fe87-9c04-5f92-42f10597df6d@nvidia.com>
Date:   Tue, 23 May 2023 14:42:52 +0100
From:   Jon Hunter <jonathanh@...dia.com>
To:     Bartosz Golaszewski <brgl@...ev.pl>
Cc:     Linus Walleij <linus.walleij@...aro.org>,
        Prathamesh Shete <pshete@...dia.com>, thierry.reding@...il.com,
        bgolaszewski@...libre.com, linux-gpio@...r.kernel.org,
        linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
        smangipudi@...dia.com, kyarlagadda@...dia.com,
        Manish Bhardwaj <mbhardwaj@...dia.com>
Subject: Re: [PATCH v3] gpio: tegra186: Check GPIO pin permission before
 access.


On 23/05/2023 10:17, Bartosz Golaszewski wrote:
> On Tue, May 23, 2023 at 8:22 AM Jon Hunter <jonathanh@...dia.com> wrote:
>>
>>
>> On 17/10/2022 10:31, Linus Walleij wrote:
>>> On Fri, Oct 7, 2022 at 7:59 AM Prathamesh Shete <pshete@...dia.com> wrote:
>>>
>>>> This change checks if we have the necessary permission to
>>>> access the GPIO. For devices that have support for virtualisation
>>>> we need to check both the TEGRA186_GPIO_VM_REG and the
>>>> TEGRA186_GPIO_SCR_REG registers. For device that do not have
>>>> virtualisation support for GPIOs we only need to check the
>>>> TEGRA186_GPIO_SCR_REG register.
>>>>
>>>> Signed-off-by: Manish Bhardwaj <mbhardwaj@...dia.com>
>>>> Signed-off-by: Prathamesh Shete <pshete@...dia.com>
>>>
>>> Very nice patch!
>>> Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
>>
>>
>> I did not see this anywhere in the mainline/next. However, I also
>> noticed that we don't have the correct email address for Bartosz (again).
>>
> 
> I have only ever changed my address in MAINTAINERS once, so "again" is
> not really the right term. And scripts/get_maintainer.pl should be
> used anyway every time when submitting patches.

Sorry I meant that WE did not send to the correct email AGAIN and not 
that you updated your email address :-)

Thanks
Jon

-- 
nvpublic

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ