netdev - Re: [PATCH net-next v3 4/8] MIPS: dts: mscc: describe the PTP ready interrupt

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: <CY4PR2201MB1272FD18679D457C981FE03BC1A70@CY4PR2201MB1272.namprd22.prod.outlook.com>
Date:   Sat, 24 Aug 2019 14:18:56 +0000
From:   Paul Burton <paul.burton@...s.com>
To:     Antoine Tenart <antoine.tenart@...tlin.com>
CC:     "davem@...emloft.net" <davem@...emloft.net>,
        "richardcochran@...il.com" <richardcochran@...il.com>,
        "alexandre.belloni@...tlin.com" <alexandre.belloni@...tlin.com>,
        "UNGLinuxDriver@...rochip.com" <UNGLinuxDriver@...rochip.com>,
        "ralf@...ux-mips.org" <ralf@...ux-mips.org>,
        Paul Burton <pburton@...ecomp.com>,
        "jhogan@...nel.org" <jhogan@...nel.org>,
        Antoine Tenart <antoine.tenart@...tlin.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
        "thomas.petazzoni@...tlin.com" <thomas.petazzoni@...tlin.com>,
        "allan.nielsen@...rochip.com" <allan.nielsen@...rochip.com>,
        "linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>
Subject: Re: [PATCH net-next v3 4/8] MIPS: dts: mscc: describe the PTP ready
  interrupt

Hello,

Antoine Tenart wrote:
> This patch adds a description of the PTP ready interrupt, which can be
> triggered when a PTP timestamp is available on an hardware FIFO.

Applied to mips-next.

> commit b4742e6682d5
> https://git.kernel.org/mips/c/b4742e6682d5
> 
> Signed-off-by: Antoine Tenart <antoine.tenart@...tlin.com>
> Signed-off-by: Paul Burton <paul.burton@...s.com>

Thanks,
    Paul

[ This message was auto-generated; if you believe anything is incorrect
  then please email paul.burton@...s.com to report it. ]