From: Richard Cochran <richardcochran@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [RFC][PATCH 0/3] net_tstamp: Add SIOCGHWTSTAMP ioctl
Date: Thu, 14 Nov 2013 08:41:19 +0100 [thread overview]
Message-ID: <20131114074118.GC4908@netboy> (raw)
In-Reply-To: <1384396635.29151.36.camel@bwh-desktop.uk.level5networks.com>
On Thu, Nov 14, 2013 at 02:37:15AM +0000, Ben Hutchings wrote:
> SIOCSHWTSTAMP returns the real configuration to the application
> using it, but there is currently no way for any other
> application to find out the configuration non-destructively.
I guess that the reasoning behind the original interface is that an
application only wants to know the settings when it needs a particular
setting in order to operate correctly. This would make the query call
pointless, since the application might as well just go ahead and set
the values that it needs.
Do you have a particular use case in mind?
Thanks,
Richard
next prev parent reply other threads:[~2013-11-14 7:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 2:37 [RFC][PATCH 0/3] net_tstamp: Add SIOCGHWTSTAMP ioctl Ben Hutchings
2013-11-14 2:38 ` [RFC][PATCH 1/3] net_tstamp: Improve kernel-doc for struct hwtstamp_config Ben Hutchings
2013-11-14 2:39 ` [RFC][PATCH 2/3] net_tstamp: Add SIOCGHWTSTAMP ioctl to match SIOCSHWTSTAMP Ben Hutchings
2013-11-14 2:40 ` [RFC][PATCH 3/3] sfc: Implement the SIOCGHWTSTAMP ioctl Ben Hutchings
2013-11-14 2:46 ` Test program for SIOC{G,S}HWTSTAMP Ben Hutchings
2013-11-14 6:51 ` David Miller
2013-11-14 6:50 ` [RFC][PATCH 0/3] net_tstamp: Add SIOCGHWTSTAMP ioctl David Miller
2013-11-14 7:41 ` Richard Cochran [this message]
2013-11-14 15:10 ` Ben Hutchings
2013-11-14 16:21 ` Richard Cochran
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=20131114074118.GC4908@netboy \
--to=richardcochran@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-net-drivers@solarflare.com \
--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).