From: alex.williamson@hp.com (Alex Williamson)
To: Linus Torvalds <torvalds@osdl.org>
Cc: Greg KH <greg@kroah.com>,
akpm@osdl.org, linux-kernel <linux-kernel@vger.kernel.org>,
sensors@Stimpy.netroedge.com
Subject: [BK PATCH] I2C update for 2.6.8-rc1
Date: Thu, 19 May 2005 06:25:12 +0000 [thread overview]
Message-ID: <1093398142.9555.9.camel@tdi> (raw)
In-Reply-To: <1093397881.9555.6.camel@tdi>
On Tue, 2004-08-24 at 19:38 -0600, Alex Williamson wrote:
> 1200-121f : motherboard
> 1200-121f : 0000:00:1f.3
BTW, this is the resource that was in conflict. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
WARNING: multiple messages have this Message-ID (diff)
From: Alex Williamson <alex.williamson@hp.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Greg KH <greg@kroah.com>,
akpm@osdl.org, linux-kernel <linux-kernel@vger.kernel.org>,
sensors@Stimpy.netroedge.com
Subject: Re: [BK PATCH] I2C update for 2.6.8-rc1
Date: Tue, 24 Aug 2004 19:42:22 -0600 [thread overview]
Message-ID: <1093398142.9555.9.camel@tdi> (raw)
In-Reply-To: <1093397881.9555.6.camel@tdi>
On Tue, 2004-08-24 at 19:38 -0600, Alex Williamson wrote:
> 1200-121f : motherboard
> 1200-121f : 0000:00:1f.3
BTW, this is the resource that was in conflict. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
next prev parent reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 0:05 [BK PATCH] I2C update for 2.6.8-rc1 Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-15 0:07 ` [PATCH] " Greg KH
2004-07-15 0:07 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-15 0:07 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-15 0:07 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-15 0:07 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-15 0:07 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-15 0:07 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-15 0:07 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-15 0:07 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-16 17:07 ` Pavel Machek
2005-05-19 6:25 ` Pavel Machek
2004-07-16 17:17 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-07-16 17:39 ` Bob Riegelmann
2005-05-19 6:25 ` Bob Riegelmann
2004-07-16 18:19 ` Adam Kropelin
2005-05-19 6:25 ` Adam Kropelin
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Philip Pokorny
2005-05-19 6:25 ` Jean Delvare
2004-07-17 14:30 ` Greg (or anyone else) one small i2c question Reinder
2004-07-30 5:40 ` --- " Reinder
2004-07-30 6:30 ` Denis Vlasenko
2004-08-25 6:44 ` Greg " Greg KH
2004-08-24 21:58 ` [BK PATCH] I2C update for 2.6.8-rc1 Alex Williamson
2005-05-19 6:25 ` Alex Williamson
2004-08-24 22:04 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-08-25 0:37 ` Linus Torvalds
2005-05-19 6:25 ` Linus Torvalds
2004-08-25 1:38 ` Alex Williamson
2005-05-19 6:25 ` Alex Williamson
2004-08-25 1:42 ` Alex Williamson [this message]
2005-05-19 6:25 ` Alex Williamson
2004-08-25 2:02 ` Linus Torvalds
2005-05-19 6:25 ` Linus Torvalds
2004-08-25 6:14 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-08-25 6:36 ` Greg KH
2005-05-19 6:25 ` 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=1093398142.9555.9.camel@tdi \
--to=alex.williamson@hp.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@Stimpy.netroedge.com \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.