linux-kernel - Re: [GIT PULL] watchdog updates for v4.12

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: <20170530112000.GA32657@spo001.leaseweb.nl>
Date:   Tue, 30 May 2017 13:20:00 +0200
From:   Wim Van Sebroeck <wim@...ana.be>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Guenter Roeck <linux@...ck-us.net>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux Watchdog Mailing List <linux-watchdog@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] watchdog updates for v4.12

Hi Geert,

> Hi Günter, Linus, Wim,
> 
> On Sun, May 14, 2017 at 5:55 AM, Guenter Roeck <linux@...ck-us.net> wrote:
> > As requested by Wim:
> >
> > Please pull watchdog updates for Linux v4.12 from signed tag:
> >
> >     git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git watchdog-for-linus-v4.12
> >
> > Note: I had to drop one of the patches affecting drivers/watchdog/iTCO_wdt.c
> > because it and some other patches affecting the same file came in from
> > another tree, causing severe and unnecessary conflicts. Other than that,
> > the tree is about two weeks old, even though it looks like some of the
> > patches are brand new.
> 
> What happened to this pull request?
> 
> It seems to have been superseded by "[GIT PULL REQUEST] watchdog - v4.12-rc1
> Fixes", which did get pulled, but the latter included less commits.
> 
> E.g. the rza_wdt driver was not included.
> In addition, it has also disappeared from linux-next?

The pull request was to late to include it in the merge window.
So we have to wait for the next merge window.
So that's why we sent in the fixes in before rc2 came out.
The other patches will be in the linux-next tree again in a couple of days.

Kind regards,
wim.