From: Rudolf Marek <r.marek-/xGekIyIa4Ap1Coe8Ar9gA@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Cc: Paul Menzel
<paulepanter-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] i2c-piix4 - Add support for secondary SMBus on AMD SB800 and AMD FCH chipsets
Date: Tue, 11 Jun 2013 21:47:12 +0200 [thread overview]
Message-ID: <51B77EC0.2020204@assembler.cz> (raw)
In-Reply-To: <20130611193539.GG3376@katana>
> Do you know if there should be something connected?
In Paul case, most likely not. In my case there is a voltage controller for the
DDR3 voltage regulator. I asked Paul test it on his SB800 system, I have the
Hudson successor..
>> Rudolf, it looks like your patch could also update the i2c files under
>> `Documentation`. At least there are some patches doing that.
>
> Do you mean 'busses/i2c-piix4'?
Yes he means that. I will add documentation to the patch.
Thanks
Rudolf
next prev parent reply other threads:[~2013-06-11 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 22:46 [PATCH] i2c-piix4 - Add support for secondary SMBus on AMD SB800 and AMD FCH chipsets Rudolf Marek
[not found] ` <5196B32D.7060501-/xGekIyIa4Ap1Coe8Ar9gA@public.gmane.org>
2013-05-23 7:35 ` Paul Menzel
2013-06-11 19:35 ` Wolfram Sang
2013-06-11 19:47 ` Rudolf Marek [this message]
[not found] ` <51B77EC0.2020204-/xGekIyIa4Ap1Coe8Ar9gA@public.gmane.org>
2013-06-17 7:16 ` Wolfram Sang
2013-06-17 21:37 ` Rudolf Marek
[not found] ` <51BF8184.8090807-/xGekIyIa4Ap1Coe8Ar9gA@public.gmane.org>
2013-06-19 9:55 ` Wolfram Sang
2013-07-14 21:17 ` [PATCH] i2c: i2c-piix4: " Rudolf Marek
[not found] ` <51E31566.2070509-/xGekIyIa4Ap1Coe8Ar9gA@public.gmane.org>
2013-08-15 13:19 ` Wolfram Sang
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=51B77EC0.2020204@assembler.cz \
--to=r.marek-/xgekiyia4ap1coe8ar9ga@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=paulepanter-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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).