From: Jeff Garzik <jeff@garzik.org>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, john.ronciak@intel.com,
jesse.brandeburg@intel.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/3] e1000: FIX: be ready for incoming irq at pci_request_irq
Date: Fri, 09 Mar 2007 12:38:41 -0500 [thread overview]
Message-ID: <45F19BA1.3090408@garzik.org> (raw)
In-Reply-To: <45F1954D.4000506@intel.com>
Kok, Auke wrote:
> Personally, I think this is really really needed. I'm surprised that you
> already didn't push this considering Andrew pulled this into -mm
> immediately.
Since it affects a fragile area of e1000 for all [e1000] users, I much
prefer to err on the side of caution. I have a history of pulling
wide-impact fixes like this, late in -rc cycle, and having yet more
breakage appear.
But if Andrew or Linus disagree, feel free to override me. This is just
area where I am intentionally over-cautious.
Jeff
prev parent reply other threads:[~2007-03-09 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 16:57 [PATCH 1/3] e1000: FIX: be ready for incoming irq at pci_request_irq Auke Kok
2007-03-06 16:57 ` [PATCH 2/3] e1000: FIX: firmware handover bits Auke Kok
2007-03-06 16:57 ` [PATCH 3/3] e1000: FIX: Stop raw interrupts disabled nag from RT Auke Kok
2007-03-09 16:46 ` [PATCH 1/3] e1000: FIX: be ready for incoming irq at pci_request_irq Jeff Garzik
2007-03-09 17:11 ` Kok, Auke
2007-03-09 17:38 ` Jeff Garzik [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=45F19BA1.3090408@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=auke-jan.h.kok@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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).