From: Jean Delvare <jdelvare@suse.de>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Alexandra Yates <alexandra.yates@linux.intel.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] i2c: i801: Adding Intel Lewisburg support for iTCO
Date: Fri, 5 Feb 2016 10:48:55 +0100 [thread overview]
Message-ID: <20160205104855.5ec3432c@endymion> (raw)
In-Reply-To: <20160204232746.GA2421@tetsubishi>
On Fri, 5 Feb 2016 00:27:46 +0100, Wolfram Sang wrote:
> On Thu, Feb 04, 2016 at 03:06:55PM -0800, Alexandra Yates wrote:
> > Starting from Intel Sunrisepoint (Skylake PCH) the iTCO watchdog
> > resources have been moved to reside under the i801 SMBus host
> > controller whereas previously they were under the LPC device.
> >
> > This patch adds Intel lewisburg SMBus support for iTCO device.
> >
> > Signed-off-by: Alexandra Yates <alexandra.yates@linux.intel.com>
>
> Please state what has changed in v2 of this patch?
Yes, Alexandra, please always include a changelog (between the ---
separator and the diffstat) when posting patch updates.
In this case there is no code change, the only change is the subject.
If I understand correctly, this is a fixup for commit
cdc5a3110e7c3ae793f367285789a6bc39c962dc ("i2c: i801: add Intel
Lewisburg device IDs") which should have included these changes. If so,
please mention it in the commit message. It may also make sense to tag
the patch for stable [v4.4].
Reviewed-by: Jean Delvare <jdelvare@suse.de>
Thanks,
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2016-02-05 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH V2] i2c: i801: Adding Intel Lewisburg support for iTCO>
2016-02-04 23:06 ` [PATCH V2] i2c: i801: Adding Intel Lewisburg support for iTCO Alexandra Yates
2016-02-04 23:27 ` Wolfram Sang
2016-02-05 9:48 ` Jean Delvare [this message]
2016-02-05 22:09 ` Alexandra Yates
2016-02-05 21:56 ` Alexandra Yates
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=20160205104855.5ec3432c@endymion \
--to=jdelvare@suse.de \
--cc=alexandra.yates@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).