From: Wolfram Sang <wsa@kernel.org>
To: Sui Chen <suichen@google.com>
Cc: linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-i2c@vger.kernel.org, joel@jms.id.au, andrew@aj.id.au,
tali.perry1@gmail.com, benjaminfair@google.com,
krellan@google.com, joe@perches.com
Subject: Re: [RFC Patch v2 0/3] I2C statistics as sysfs attributes
Date: Fri, 3 Dec 2021 17:37:34 +0100 [thread overview]
Message-ID: <YapHznDoqJ+wjx8m@kunai> (raw)
In-Reply-To: <20211203023728.3699610-1-suichen@google.com>
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
On Thu, Dec 02, 2021 at 06:37:25PM -0800, Sui Chen wrote:
> Add I2C statistics such as Bus Error counts and NACK counts as sysfs
> attributes so they don't need to live in debugfs.
What has changed since v1?
From a glimpse, none of my questions to v1 have been answered or
addressed?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@kernel.org>
To: Sui Chen <suichen@google.com>
Cc: benjaminfair@google.com, andrew@aj.id.au,
openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
tali.perry1@gmail.com, krellan@google.com, joe@perches.com,
linux-i2c@vger.kernel.org
Subject: Re: [RFC Patch v2 0/3] I2C statistics as sysfs attributes
Date: Fri, 3 Dec 2021 17:37:34 +0100 [thread overview]
Message-ID: <YapHznDoqJ+wjx8m@kunai> (raw)
In-Reply-To: <20211203023728.3699610-1-suichen@google.com>
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
On Thu, Dec 02, 2021 at 06:37:25PM -0800, Sui Chen wrote:
> Add I2C statistics such as Bus Error counts and NACK counts as sysfs
> attributes so they don't need to live in debugfs.
What has changed since v1?
From a glimpse, none of my questions to v1 have been answered or
addressed?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-12-03 16:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 2:37 [RFC Patch v2 0/3] I2C statistics as sysfs attributes Sui Chen
2021-12-03 2:37 ` Sui Chen
2021-12-03 2:37 ` [RFC Patch v2 1/3] i2c debug counters " Sui Chen
2021-12-03 2:37 ` Sui Chen
2021-12-03 2:50 ` Joe Perches
2021-12-03 2:50 ` Joe Perches
2021-12-03 5:35 ` Sui Chen
2021-12-03 5:35 ` Sui Chen
2021-12-03 5:54 ` Joe Perches
2021-12-03 5:54 ` Joe Perches
2021-12-03 12:36 ` kernel test robot
2021-12-03 14:18 ` kernel test robot
2021-12-03 2:37 ` [RFC Patch v2 2/3] i2c: npcm7xx: add tx_complete counter Sui Chen
2021-12-03 2:37 ` Sui Chen
2021-12-03 2:37 ` [RFC Patch v2 3/3] add npcm7xx debug counters as sysfs attributes Sui Chen
2021-12-03 2:37 ` Sui Chen
2021-12-03 21:15 ` kernel test robot
2021-12-03 16:37 ` Wolfram Sang [this message]
2021-12-03 16:37 ` [RFC Patch v2 0/3] I2C statistics " Wolfram Sang
2021-12-07 16:00 ` Sui Chen
2022-01-03 9:44 ` Wolfram Sang
2022-01-03 9:44 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2021-12-05 0:40 [RFC Patch v2 1/3] i2c debug counters " kernel test robot
2021-12-06 14:03 ` Dan Carpenter
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=YapHznDoqJ+wjx8m@kunai \
--to=wsa@kernel.org \
--cc=andrew@aj.id.au \
--cc=benjaminfair@google.com \
--cc=joe@perches.com \
--cc=joel@jms.id.au \
--cc=krellan@google.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=suichen@google.com \
--cc=tali.perry1@gmail.com \
/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.