From: Chris Novakovic <chris@chrisn.me.uk>
To: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Cc: Chris Novakovic <chris@chrisn.me.uk>
Subject: [PATCH 0/8] ipconfig: NTP server support, bug fixes, documentation improvements
Date: Tue, 17 Apr 2018 21:58:22 +0100 [thread overview]
Message-ID: <20180417205830.1812-1-chris@chrisn.me.uk> (raw)
This series (against net-next) makes various improvements to ipconfig.
It was mistakenly posted on 2018-04-07, while net-next was closed; it
still applies cleanly.
- Patch #1 correctly documents the behaviour of parameter 4 in the
"ip=" and "nfsaddrs=" command line parameter.
- Patch #2 tidies up the printk()s for reporting configured name
servers.
- Patch #3 fixes a bug in autoconfiguration via BOOTP whereby the IP
addresses of IEN-116 name servers are requested from the BOOTP
server, rather than those of DNS name servers.
- Patch #4 requests the number of DNS servers specified by
CONF_NAMESERVERS_MAX when autoconfiguring via BOOTP, rather than
hardcoding it to 2.
- Patch #5 fully documents the contents and format of /proc/net/pnp in
Documentation/filesystems/nfs/nfsroot.txt.
- Patch #6 fixes a bug whereby bogus information is written to
/proc/net/pnp when ipconfig is not used.
- Patch #7 allows for NTP servers to be configured (manually on the
kernel command line or automatically via DHCP), enabling systems with
an NFS root filesystem to synchronise their clock before mounting
their root filesystem.
Chris Novakovic (8):
ipconfig: Document setting of NIS domain name
ipconfig: Tidy up reporting of name servers
ipconfig: BOOTP: Don't request IEN-116 name servers
ipconfig: BOOTP: Request CONF_NAMESERVERS_MAX name servers
ipconfig: Document /proc/net/pnp
ipconfig: Correctly initialise ic_nameservers
ipconfig: Write NTP server IPs to /proc/net/ntp
CREDITS: Add Chris Novakovic
CREDITS | 4 +
Documentation/filesystems/nfs/nfsroot.txt | 70 ++++++++++++++---
net/ipv4/ipconfig.c | 121 +++++++++++++++++++++++++++---
3 files changed, 174 insertions(+), 21 deletions(-)
--
2.14.1
next reply other threads:[~2018-04-17 20:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 20:58 Chris Novakovic [this message]
2018-04-17 20:58 ` [PATCH 1/8] ipconfig: Document setting of NIS domain name Chris Novakovic
2018-04-17 20:58 ` [PATCH 2/8] ipconfig: Tidy up reporting of name servers Chris Novakovic
2018-04-17 20:58 ` [PATCH 3/8] ipconfig: BOOTP: Don't request IEN-116 " Chris Novakovic
2018-04-17 20:58 ` [PATCH 4/8] ipconfig: BOOTP: Request CONF_NAMESERVERS_MAX " Chris Novakovic
2018-04-17 20:58 ` [PATCH 5/8] ipconfig: Document /proc/net/pnp Chris Novakovic
2018-04-17 20:58 ` [PATCH 6/8] ipconfig: Correctly initialise ic_nameservers Chris Novakovic
2018-04-17 20:58 ` [PATCH 7/8] ipconfig: Write NTP server IPs to /proc/net/ntp Chris Novakovic
2018-04-17 20:58 ` [PATCH 8/8] CREDITS: Add Chris Novakovic Chris Novakovic
2018-04-17 21:08 ` Cong Wang
2018-04-18 17:59 ` [PATCH 0/8] ipconfig: NTP server support, bug fixes, documentation improvements David Miller
2018-04-18 18:06 ` Chris Novakovic
2018-04-18 18:12 ` Chris Novakovic
-- strict thread matches above, loose matches on Subject: below --
2018-04-07 4:08 Chris Novakovic
2018-04-07 16:29 ` David Miller
2018-04-07 17:49 ` 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=20180417205830.1812-1-chris@chrisn.me.uk \
--to=chris@chrisn.me.uk \
--cc=davem@davemloft.net \
--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).