From: David Miller <davem@davemloft.net>
To: chris@chrisn.me.uk
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/8] ipconfig: NTP server support, bug fixes, documentation improvements
Date: Sat, 07 Apr 2018 12:29:34 -0400 (EDT) [thread overview]
Message-ID: <20180407.122934.1066979747676984647.davem@davemloft.net> (raw)
In-Reply-To: <20180407040903.8997-1-chris@chrisn.me.uk>
From: Chris Novakovic <chris@chrisn.me.uk>
Date: Sat, 7 Apr 2018 05:08:55 +0100
> This series (against net-next) makes various improvements to ipconfig:
The net-next tree is closed at this time, please resubmit this series
when that tree opens up again.
Thank you.
next prev parent reply other threads:[~2018-04-07 16:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 4:08 [PATCH 0/8] ipconfig: NTP server support, bug fixes, documentation improvements Chris Novakovic
2018-04-07 4:08 ` [PATCH 1/8] ipconfig: Document setting of NIS domain name Chris Novakovic
2018-04-07 4:08 ` [PATCH 2/8] ipconfig: Tidy up reporting of name servers Chris Novakovic
2018-04-07 4:08 ` [PATCH 3/8] ipconfig: BOOTP: Don't request IEN-116 " Chris Novakovic
2018-04-07 4:08 ` [PATCH 4/8] ipconfig: BOOTP: Request CONF_NAMESERVERS_MAX " Chris Novakovic
2018-04-07 4:09 ` [PATCH 5/8] ipconfig: Document /proc/net/pnp Chris Novakovic
2018-04-07 4:09 ` [PATCH 6/8] ipconfig: Correctly initialise ic_nameservers Chris Novakovic
2018-04-07 4:09 ` [PATCH 7/8] ipconfig: Write NTP server IPs to /proc/net/ntp Chris Novakovic
2018-04-07 15:25 ` Chris Novakovic
2018-04-07 15:28 ` [PATCH v2 " Chris Novakovic
2018-04-07 4:09 ` [PATCH 8/8] CREDITS: Add Chris Novakovic Chris Novakovic
2018-04-07 16:29 ` David Miller [this message]
2018-04-07 17:49 ` [PATCH 0/8] ipconfig: NTP server support, bug fixes, documentation improvements Chris Novakovic
-- strict thread matches above, loose matches on Subject: below --
2018-04-17 20:58 Chris Novakovic
2018-04-18 17:59 ` David Miller
2018-04-18 18:06 ` Chris Novakovic
2018-04-18 18:12 ` Chris Novakovic
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=20180407.122934.1066979747676984647.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chris@chrisn.me.uk \
--cc=netdev@vger.kernel.org \
/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).