linux-kernel - Re: (subset) [PATCH v4 1/2] rtc: m48t59: Use platform

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: <e6dbc3e6-5305-7c00-90e7-3d06b1b5e459@linux-m68k.org>
Date: Fri, 22 Nov 2024 09:24:36 +1100 (AEDT)
From: Finn Thain <fthain@...ux-m68k.org>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>
cc: Geert Uytterhoeven <geert@...ux-m68k.org>, 
    "David S. Miller" <davem@...emloft.net>, 
    Andreas Larsson <andreas@...sler.com>, Daniel Palmer <daniel@...f.com>, 
    Michael Pavone <pavone@...rodev.com>, linux-m68k@...ts.linux-m68k.org, 
    linux-rtc@...r.kernel.org, sparclinux@...r.kernel.org, 
    linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v4 1/2] rtc: m48t59: Use platform_data struct
 for year offset value


On Thu, 21 Nov 2024, Alexandre Belloni wrote:

> On 21/11/2024 09:13:32+1100, Finn Thain wrote:
> > 
> > On Mon, 18 Nov 2024, Alexandre Belloni wrote:
> > 
> > > On Wed, 13 Nov 2024 09:32:15 +1100, Finn Thain wrote:
> > > > Instead of hard-coded values and ifdefs, store the year offset in the
> > > > platform_data struct.
> > > > 
> > > > 
> > > 
> > > Applied, thanks!
> > > 
> > > [1/2] rtc: m48t59: Use platform_data struct for year offset value
> > >       https://git.kernel.org/abelloni/c/a06e4a93067c
> > > 
> > 
> > Thanks, Alexandre. Would you also take patch 2/2, please? Geert has sent a 
> > reviewed-by tag for that one too.
> 
> I thought Geert would take it as this only touches arch/m68k
> 

That's quite understandable -- I accidentally addressed it "To: Geert". 
Sorry for any confusion caused.

Anyway, would you please pick up patch 2/2 also? After all, patch 2/2 is 
the reason why patch 1/2 exists. Indeed, 1/2 was written several years 
after 2/2, in response to your recent review of 2/2.