From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] e1000e: Use deferrable timer for watchdog
Date: Thu, 20 Dec 2007 10:49:22 -0800 [thread overview]
Message-ID: <476AB932.8050606@intel.com> (raw)
In-Reply-To: <82e4877d0712200956l4126e221qc0cf4720e59ca2a1@mail.gmail.com>
Parag Warudkar wrote:
> On Dec 20, 2007 12:05 PM, Kok, Auke <auke-jan.h.kok@intel.com> wrote:
>> I can't even apply this patch and the e1000 one... not only is it whitespace
>> damaged it is also not properly formatted as patch at all. If you want me to take
>> these patches seriously, then please fix the formatting issues.
>
> Sigh - I use Pine, follow Documents/email-clients.txt for the
> recommended settings and obviously the pathces are not generated with
> whitespace damage at my end as I test those before sending out.
>
> So although I hate to see this happen there is nothing at this moment
> that I can do - except for attaching the patch instead of inlining it.
> Since they have already been reviewed inline, please see if the
> attached patches work for you.
here's what the files in my Maildir spool look like in vim (my vim displays a '»'
char for tabs and a "¶" for EOL):
76 --- linux-2.6/drivers/net/e1000e/netdev.c» 2007-12-07 10:04:39.00000000
77 +++ linux-2.6-work/drivers/net/e1000e/netdev.c» 2007-12-18 20:45:59.00000000
78 @@ -3899,7 +3899,7 @@¶
79 » » goto err_eeprom;¶
80 » }¶
81 ¶
82 -» init_timer(&adapter->watchdog_timer);¶
83 +» init_timer_deferrable(&adapter->watchdog_timer);¶
84 » adapter->watchdog_timer.function = &e1000_watchdog;¶
85 » adapter->watchdog_timer.data = (unsigned long) adapter;¶
86 ¶
87 --¶
notice that there are two spaces instead of 1. Also there's no line heading the
diff with 'diff a/foo b/foo' which is what throws of stg. And the -p option is
missing.
as for content, the patch looks OK with me. I ran the numbers and allthough there
was a slight average delay in the link up detection time it is negligeable (less
than 0.2sec difference over a bunch of measurements), and I confirmed your
powertop numbers are correct. As for the timer interval, the watchdog may already
be delayed up to 3 seconds safely, this doesn't change that.
I'll forward the patch, Care to make one for e100? plenty of laptops with those
still around! The embedded guys would love it I think.
Thanks,
Auke
prev parent reply other threads:[~2007-12-20 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 1:49 [PATCH] e1000e: Use deferrable timer for watchdog Parag Warudkar
2007-12-19 19:04 ` Kok, Auke
2007-12-20 17:05 ` Kok, Auke
2007-12-20 17:56 ` Parag Warudkar
2007-12-20 18:49 ` Kok, Auke [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=476AB932.8050606@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=parag.warudkar@gmail.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).