From: Mark Huth <mhuth@mvista.com>
To: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
netdev@vger.kernel.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] e1000 stop raw interrupts disabled nag from RT
Date: Thu, 01 Mar 2007 14:58:10 -0700 [thread overview]
Message-ID: <45E74C72.1020107@mvista.com> (raw)
In-Reply-To: <45E70959.4070209@stud.feec.vutbr.cz>
Michal Schmidt wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Kok, Auke wrote:
>
>> Mark Huth wrote:
>>
>>> Well, I'm not an expert on the realtime patches - but most any patch set
>>> from Ingo seems to set this off - we've run through a bunch all the way
>>> since 2.6.10.
>>>
>> that's bizarre, and would imply that Ingo himself never spotted this in ages,
>> not to mention never tell us about it?
>>
>
> Ingo's -rt patches have contained this change to e1000 for some time.
> The code is perfectly fine as is for non-RT kernels, so maybe that's why
> noone felt like telling you about it.
>
> Michal
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
> Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org
>
> iD8DBQFF5wlZabKV90ewf0QRAse3AJ979xur0u8X1DokSzaAMvLQCWPkXACfU9ss
> xC05DAbFNAaFMLnQrzBKit0=
> =I5mt
> -----END PGP SIGNATURE-----
>
Ah, tis true indeed. This only shows up when one brings a newer driver
forward after the RT patch has been applied. I guess you would need to
coordinate this with Ingo.
Thanks,
Mark Huth
prev parent reply other threads:[~2007-03-01 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 2:54 [PATCH] e1000 stop raw interrupts disabled nag from RT Mark Huth
2007-03-01 3:18 ` Kok, Auke
2007-03-01 4:59 ` Mark Huth
2007-03-01 16:55 ` Kok, Auke
2007-03-01 17:11 ` Michal Schmidt
2007-03-01 17:29 ` Kok, Auke
2007-03-01 17:34 ` Michal Schmidt
2007-03-01 21:58 ` Mark Huth [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=45E74C72.1020107@mvista.com \
--to=mhuth@mvista.com \
--cc=auke-jan.h.kok@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=xschmi00@stud.feec.vutbr.cz \
/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).