From: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
To: "Roland Dreier" <roland@topspin.com>
Cc: "Zwane Mwaikambo" <zwane@arm.linux.org.uk>,
<linux-kernel@vger.kernel.org>,
"Nguyen, Tom L" <tom.l.nguyen@intel.com>,
"Greg KH" <greg@kroah.com>
Subject: RE: [PATCH] PCI: Clean up printks in msi.c
Date: Mon, 10 Jan 2005 10:33:00 -0800 [thread overview]
Message-ID: <C7AB9DA4D0B1F344BF2489FA165E5024076EEB2F@orsmsx404.amr.corp.intel.com> (raw)
On Monday, January 10, 2005 9:39 AM, Roland Dreier wrote:
> No problem, here's the patch without any "success" message.
Look great.
Thanks,
Long
next reply other threads:[~2005-01-10 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 18:33 Nguyen, Tom L [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-17 22:01 [PATCH] PCI: pci_ids.h correction for Intel ICH7 - 2.6.10-bk13 Greg KH
2005-01-17 22:01 ` [PATCH] PCI: Clean up printks in msi.c Greg KH
2005-01-10 17:11 Roland Dreier
2005-01-10 17:23 ` Zwane Mwaikambo
2005-01-10 17:31 ` Greg KH
2005-01-10 17:39 ` Roland Dreier
2005-01-12 0:37 ` Greg KH
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=C7AB9DA4D0B1F344BF2489FA165E5024076EEB2F@orsmsx404.amr.corp.intel.com \
--to=tom.l.nguyen@intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@topspin.com \
--cc=zwane@arm.linux.org.uk \
/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).