Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 17 Jan 2022 18:34:30 +0100
From:   Dominik Brodowski <linux@dominikbrodowski.net>
To:     "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc:     linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] random: selectively clang-format where it makes sense
Message-ID: <YeWopoOFYaHfBgE2@owl.dominikbrodowski.net>
References: <20220113154413.29513-1-Jason@zx2c4.com>
 <20220116163547.154991-1-Jason@zx2c4.com>
 <20220116163547.154991-4-Jason@zx2c4.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220116163547.154991-4-Jason@zx2c4.com>
Precedence: bulk

Am Sun, Jan 16, 2022 at 05:35:47PM +0100 schrieb Jason A. Donenfeld:
> This is an old driver that has seen a lot of different eras of kernel
> coding style. In an effort to make it easier to code for, unify the
> coding style around the current norm, by accepting some of -- but
> certainly not all of -- the suggestions from clang-format. This should
> remove ambiguity in coding style, especially with regards to spacing,
> when code is being changed or amended. Consequently it also makes code
> review easier on the eyes, following one uniform style rather than
> several.
> 
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

	Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>

Thanks,
	Dominik