linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Walker <danielwa@cisco.com>
To: "xe-kernel@external.cisco.com" <xe-kernel@external.cisco.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jean Delvare <khali@linux-fr.org>,
	Guenter Roeck <linux@roeck-us.net>,
	lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: unstable /sys interface from hmon
Date: Mon, 30 Jan 2017 12:37:14 -0800	[thread overview]
Message-ID: <99aae36e-ddfd-dcd2-e544-9c28ae373959@cisco.com> (raw)

Hi,

Cisco recently upgraded to kernel 4.4.. We have applications which use the /sys interfaces for some hmon drivers.
We found that the following patches,

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bab2243ce1897865e31ea6d59b0478391f51812b
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c3b7cddc70075d525db6b3068d8b2b9158eedc84

Altered the interface as seen from userspace. These patches changed the paths in the following way,

Before,
/sys/bus/i2c/devices/14-0050/

After,
/sys/bus/i2c/devices/14-0050/hwmon/hwmon7

My impression was that /sys was suppose to be stable, and debugfs was unstable. I'm not sure what the current guidelines are
for this, but we would request that hmon drivers maintain a stable interface from /sys. This change has cause upgrade issues
for us which we would like to avoid in the future.

A patch to add in a compatibility layer would be welcome.

Daniel

             reply	other threads:[~2017-01-30 20:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 20:37 Daniel Walker [this message]
2017-01-30 23:11 ` unstable /sys interface from hmon Guenter Roeck

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=99aae36e-ddfd-dcd2-e544-9c28ae373959@cisco.com \
    --to=danielwa@cisco.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lm-sensors@lm-sensors.org \
    --cc=xe-kernel@external.cisco.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 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).