From: "David S. Miller" <davem@davemloft.net>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@oss.sgi.com, hadi@cyberus.ca
Subject: Re: [PATCH 2.6 4/4]: ipt: convert jiffie values to USER_HZ when dumping
Date: Fri, 5 Nov 2004 16:57:52 -0800 [thread overview]
Message-ID: <20041105165752.3dee2876.davem@davemloft.net> (raw)
In-Reply-To: <418ABA6C.8060402@trash.net>
All 4 patches applied, thanks Patrick.
BTW, you don't need to split up changes like this with such high
granularity. It's perfectly fine to lump these kinds of simple
changes together as "Convert to USER_HZ when dumping in TC action
modules".
If the transformation is sizable or of non-trivial complexity, then
yes splitting up the individual changes makes sense and makes it easier
for people to review and verify the patches.
Just a FYI. :-)
prev parent reply other threads:[~2004-11-06 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 23:25 [PATCH 2.6 4/4]: ipt: convert jiffie values to USER_HZ when dumping Patrick McHardy
2004-11-06 0:57 ` David S. Miller [this message]
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=20041105165752.3dee2876.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@oss.sgi.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).