linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: Linux I2C <linux-i2c@vger.kernel.org>, Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH] i2c: Update the description of I2C_SMBUS
Date: Mon, 18 Jul 2016 17:36:15 +0200	[thread overview]
Message-ID: <20160718153605.GR4663@mail.corp.redhat.com> (raw)
In-Reply-To: <20160718123943.255b6599@endymion>

On Jul 18 2016 or thereabouts, Jean Delvare wrote:
> We support the SMBus Host Notify protocol now.
> 
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> Cc: Wolfram Sang <wsa@the-dreams.de>

Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>

Cheers,
Benjamin

> ---
>  drivers/i2c/Kconfig |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> --- linux-4.7-rc7.orig/drivers/i2c/Kconfig	2016-07-04 08:01:00.000000000 +0200
> +++ linux-4.7-rc7/drivers/i2c/Kconfig	2016-07-18 12:34:11.058067963 +0200
> @@ -88,8 +88,8 @@ config I2C_SMBUS
>  	tristate "SMBus-specific protocols" if !I2C_HELPER_AUTO
>  	help
>  	  Say Y here if you want support for SMBus extensions to the I2C
> -	  specification. At the moment, the only supported extension is
> -	  the SMBus alert protocol.
> +	  specification. At the moment, two extensions are supported:
> +	  the SMBus Alert protocol and the SMBus Host Notify protocol.
>  
>  	  This support is also available as a module.  If so, the module
>  	  will be called i2c-smbus.
> 
> 
> -- 
> Jean Delvare
> SUSE L3 Support

  reply	other threads:[~2016-07-18 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18 10:39 [PATCH] i2c: Update the description of I2C_SMBUS Jean Delvare
2016-07-18 15:36 ` Benjamin Tissoires [this message]
2016-07-18 18:12 ` 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=20160718153605.GR4663@mail.corp.redhat.com \
    --to=benjamin.tissoires@redhat.com \
    --cc=jdelvare@suse.de \
    --cc=linux-i2c@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).