linux-kernel - Re: [PATCH v2] ARM: dts: aspeed: update Hr855xg2 device tree

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] [day] [month] [year] [list]

Message-Id: <1c13de6c-3bee-4afc-8a03-691222b07ebe@www.fastmail.com>
Date:   Fri, 24 Jan 2020 10:31:30 +1030
From:   "Andrew Jeffery" <andrew@...id.au>
To:     "Andrew Peng" <pengms1@...ovo.com>,
        "Benjamin Fair" <benjaminfair@...gle.com>,
        linux-kernel@...r.kernel.org, linux-aspeed@...ts.ozlabs.org,
        linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
        mark.rutland@....com, "Rob Herring" <robh+dt@...nel.org>
Cc:     openbmc@...ts.ozlabs.org, "Derek Lin" <dlin23@...ovo.com>,
        "Harry Sung1" <hsung1@...ovo.com>
Subject: Re: [PATCH v2] ARM: dts: aspeed: update Hr855xg2 device tree

On Thu, 23 Jan 2020, at 19:21, Andrew Peng wrote:
> Update i2c aliases.
> Change flash_memory mapping address and size.
> Add in a gpio-keys section.
> Add in a peci0 section.
> Update i2c0,i2c0 and i2c11 section.
> Enable vhub, vuart, spi1 and spi2.
> Remove gpio from gpio section since it controlled by user space.

These seem like largely independent items. I'd prefer that you have
one commit for each item in the list, that way it's easier to review
and understand the relationships between the bits of affected code.
Basically, don't give people reasons to say no to your patches :) The
smaller and more coherent the change, the easier it is to give it a
Reviewed-by or Acked-by tag.

Also commit messages should say _why_ you're making the changes
not _what_ changes you're making. The diff tells us _what_, but nothing
besides comments and the commit message can tell us why. It's much
more convincing if you explain why your patch must be applied.

Andrew