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]
Date:   Mon, 18 Jul 2022 14:49:15 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     kris@...eddedTS.com, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Cc:     Shawn Guo <shawnguo@...nel.org>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        Fabio Estevam <festevam@...il.com>,
        NXP Linux Team <linux-imx@....com>,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org,
        Mark Featherston <mark@...eddedTS.com>
Subject: Re: [RFC PATCH v2] ARM: dts: Add TS-7553-V2 support

On 15/07/2022 19:54, Kris Bahnsen wrote:
> On Fri, 2022-07-15 at 08:42 +0200, Krzysztof Kozlowski wrote:
>> On 14/07/2022 23:26, Kris Bahnsen wrote:
>>> On Thu, 2022-07-14 at 10:34 +0200, Krzysztof Kozlowski wrote:
>>>> On 14/07/2022 00:12, Kris Bahnsen wrote:
>>>>> Add initial support of the i.MX6UL based TS-7553-V2 platform.
>>>>
>>>> Use subject prefix matching the subsystem. git log --oneline --
>>>
>>> Can you please elaborate? The subject prefix is "ARM: dts:", I'm not
>>> sure what is missing. Should it be something like
>>> "ARM: dts: imx6ul-ts7553v2:" in this case?
>>
>> Run the command, you will see.
> 
> I had previously run the command and the output of it did not make sense in
> the context of your prior comment. Forgive my ignorance, but I'd like to
> understand specifically what you mean here so we can do the correct thing
> in the future.
> 
> $ git log --oneline -- | head -n 20

This obviously does not make sense. -- as you can read in git log help
and several other Unix/Linux commands is marking path arguments. You
want to run it on specific subsystem, don't you?

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ