From: "Bob Beers" <bob.beers@gmail.com>
To: "Varun Chandramohan" <varunc@linux.vnet.ibm.com>
Cc: "Stephen Hemminger" <shemminger@linux-foundation.org>,
davem@davemloft.net, netdev@vger.kernel.org, kaber@trash.net,
socketcan@hartkopp.net, krkumar2@in.ibm.com, varuncha@in.ibm.com
Subject: Re: [PATCH 2/4 - rev2] Add new timeval_to_sec function
Date: Tue, 21 Aug 2007 05:58:58 -0400 [thread overview]
Message-ID: <4f6ba3b0708210258k779ff97x87edbb4ace091d0e@mail.gmail.com> (raw)
In-Reply-To: <46CA5E75.9050904@linux.vnet.ibm.com>
What if the name of the function was more descriptive of what the
function actually does? Maybe timeval_ceil_sec()?
next prev parent reply other threads:[~2007-08-21 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 8:15 [PATCH 2/4 - rev2] Add new timeval_to_sec function Varun Chandramohan
2007-08-20 14:53 ` Stephen Hemminger
2007-08-21 3:39 ` Varun Chandramohan
2007-08-21 9:58 ` Bob Beers [this message]
2007-08-21 11:09 ` Varun Chandramohan
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=4f6ba3b0708210258k779ff97x87edbb4ace091d0e@mail.gmail.com \
--to=bob.beers@gmail.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=krkumar2@in.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=socketcan@hartkopp.net \
--cc=varunc@linux.vnet.ibm.com \
--cc=varuncha@in.ibm.com \
/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).