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] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200305.180823.1274906337509861200.davem@davemloft.net>
Date:   Thu, 05 Mar 2020 18:08:23 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     sfr@...b.auug.org.au
Cc:     sameo@...ux.intel.com, linux-next@...r.kernel.org,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        johannes@...solutions.net
Subject: Re: linux-next: the nfc-next tree seems to be old

From: Stephen Rothwell <sfr@...b.auug.org.au>
Date: Fri, 6 Mar 2020 10:48:25 +1100

> On Thu, 30 Jan 2020 10:55:38 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>
>> Hi Samuel,
>> 
>> I noticed that the nfc-next tree has not changed since June 2018 and
>> has been orphaned in May 2019, so am wondering if the commits in it are
>> still relevant or should I just remove the tree from linux-next.
> 
> Since I have had no response, I will remove it tomorrow.

We've been integrating NFC patches directly into my networking tree for
a while now, so this is indeed the thing to do.

Thanks.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ