From: Wolfram Sang <wsa@the-dreams.de>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] kernfs: remove outdated and confusing comment
Date: Wed, 11 Mar 2015 13:15:54 +0000 [thread overview]
Message-ID: <20150311131554.GA10067@katana> (raw)
In-Reply-To: <20150311114531.GB25944@htj.duckdns.org>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
> Hmm... poll isn't hooked up for bin files and the behavior isn't well
Ah, thanks! I assumed something like that but could not find the
relevant code.
> defined either. The open file's event counter is never synchronized
> to the backing node's. Before the first kernfs_notify(), it won't
> trigger and after always. We'll prolly need to define that better.
> What's the use case that you're interested in?
I wanted to add notification to drivers/i2c/i2c-slave-eeprom.c which is
a software backend when the Linux system is acting as an I2C slave
device. This is basically a dual mem driver. One side is exposed to the
system as a bin-file in sysfs. The other side is accessible like an
EEPROM for other I2C masters connected to the bus. The notification
should report to userspace when a remote master has written something
to us so the memory contents changed.
I know this is not the best way of notification because we don't know
what changed and would need to compare. However, the whole I2C slave
framework is still very young and I wanted to play with it for the case
where only a few bytes are exposed.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-11 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 10:26 [PATCH] kernfs: remove outdated and confusing comment Wolfram Sang
2015-03-11 11:45 ` Tejun Heo
2015-03-11 13:15 ` Wolfram Sang [this message]
2015-04-23 12:51 ` Wolfram Sang
2015-04-23 14:56 ` Tejun Heo
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=20150311131554.GA10067@katana \
--to=wsa@the-dreams.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=tj@kernel.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).