From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: sameo@linux.intel.com, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
johannes@sipsolutions.net
Subject: Re: linux-next: the nfc-next tree seems to be old
Date: Thu, 05 Mar 2020 18:08:23 -0800 (PST) [thread overview]
Message-ID: <20200305.180823.1274906337509861200.davem@davemloft.net> (raw)
In-Reply-To: <20200306104825.068268eb@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 6 Mar 2020 10:48:25 +1100
> On Thu, 30 Jan 2020 10:55:38 +1100 Stephen Rothwell <sfr@canb.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.
next prev parent reply other threads:[~2020-03-06 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 23:55 linux-next: the nfc-next tree seems to be old Stephen Rothwell
2020-03-05 23:48 ` Stephen Rothwell
2020-03-06 2:08 ` David Miller [this message]
2020-03-07 3:45 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200305.180823.1274906337509861200.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).