linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Hansen <hansens@google.com>
To: linux-i2c@vger.kernel.org
Cc: Sam Hansen <hansens@google.com>,
	wsa@the-dreams.de, corbet@lwn.net, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v3 3/3] Documentation/i2c: adopt kernel commenting style in examples
Date: Fri, 13 Apr 2018 10:42:57 -0700	[thread overview]
Message-ID: <20180413174257.139182-3-hansens@google.com> (raw)
In-Reply-To: <20180413174257.139182-1-hansens@google.com>

The example I2C code is rewritten to adopt the preferred kernel block
commenting style.

Signed-off-by: Sam Hansen <hansens@google.com>
---
Changes from v2:
  1. only the block comment is updated.
  2. one-line comments are reverted to prior form.

 Documentation/i2c/dev-interface | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Documentation/i2c/dev-interface b/Documentation/i2c/dev-interface
index f92ee1f59914..fbed645ccd75 100644
--- a/Documentation/i2c/dev-interface
+++ b/Documentation/i2c/dev-interface
@@ -67,8 +67,10 @@ the device supports them. Both are illustrated below.
     /* res contains the read word */
   }
 
-  /* Using I2C Write, equivalent of
-     i2c_smbus_write_word_data(file, reg, 0x6543) */
+  /*
+   * Using I2C Write, equivalent of
+   * i2c_smbus_write_word_data(file, reg, 0x6543)
+   */
   buf[0] = reg;
   buf[1] = 0x43;
   buf[2] = 0x65;
-- 
2.17.0.484.g0c8726318c-goog

  parent reply	other threads:[~2018-04-13 17:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13 17:42 [PATCH v3 1/3] Documentation/i2c: whitespace cleanup Sam Hansen
2018-04-13 17:42 ` [PATCH v3 2/3] Documentation/i2c: sync docs with current state of i2c-tools Sam Hansen
2018-04-18  8:09   ` Wolfram Sang
2018-04-18  8:21   ` Wolfram Sang
2018-04-18 18:17     ` Sam Hansen
2018-04-13 17:42 ` Sam Hansen [this message]
2018-04-18  8:10   ` [PATCH v3 3/3] Documentation/i2c: adopt kernel commenting style in examples Wolfram Sang
2018-04-18  8:08 ` [PATCH v3 1/3] Documentation/i2c: whitespace cleanup 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=20180413174257.139182-3-hansens@google.com \
    --to=hansens@google.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --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).