linux-kernel - Re: [PATCH v4 2/2] m68k: mvme147, mvme16x: Adopt rtc-m48t59 platform driver

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: <CAMuHMdVjTgssYR0RAsxpejRcUnPb7biT0kuq+Xc5T2TcPsahiw@mail.gmail.com>
Date: Sun, 24 Nov 2024 10:42:28 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc: Finn Thain <fthain@...ux-m68k.org>, Daniel Palmer <daniel@...f.com>, 
	Michael Pavone <pavone@...rodev.com>, linux-m68k@...ts.linux-m68k.org, 
	linux-rtc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 2/2] m68k: mvme147, mvme16x: Adopt rtc-m48t59 platform driver

Hi Alexandre,

On Sat, Nov 23, 2024 at 12:03 AM Alexandre Belloni
<alexandre.belloni@...tlin.com> wrote:
> On 22/11/2024 15:44:33+0100, Geert Uytterhoeven wrote:
> > On Tue, Nov 12, 2024 at 11:51 PM Finn Thain <fthain@...ux-m68k.org> wrote:
> > > Both mvme147 and mvme16x platforms have their own RTC driver
> > > implementations that duplicate functionality provided by the rtc-m48t59
> > > driver. Adopt the rtc-m48t59 driver and remove the other ones.
> > >
> > > Tested-by: Daniel Palmer <daniel@...f.com>
> > > Signed-off-by: Finn Thain <fthain@...ux-m68k.org>
> > > Reviewed-by: Geert Uytterhoeven <geert@...ux-m68k.org>
> > > ---
> > > This patch depends upon the m48t59 driver changes in the preceding patch.
> > >
> > > Changed since v1:
> > >  - Initialize yy_offset in struct m48t59_plat_data.
> > >
> > > Changed Since v3:
> > >  - Re-ordered defconfig symbols.
> > >  - Added reviewed-by tag from arch maintainer.
> >
> > Acked-by: Geert Uytterhoeven <geert@...ux-m68k.org>
> > so it still can make it into v6.13-rc1 via RTC?
>
> It is now applied, it is going to conflict with your tree as it didn't
> cleanly apply. I don't think this is going to cause issues but I'll let
> it sit in linux-next for a few days before sending to Linus.

Thanks! It indeed conflicts with what I sent to Linus, and thus with
Linus' current tree, due to nearby changes. If you think the conflict
is too serious, feel free to drop the commit, and I'll pick it up
for v6.14-rc1.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds