From: matthieu castet <castet.matthieu@free.fr>
To: chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil>
Cc: netdev@oss.sgi.com, linux-atm-general@lists.sourceforge.net,
usbatm@lists.infradead.org
Subject: Re: [Linux-ATM-General] [RFC][PATCH] Very basic sysfs support for ATM devices (updated)
Date: Fri, 04 Feb 2005 19:27:07 +0100 [thread overview]
Message-ID: <4203BE7B.2030503@free.fr> (raw)
In-Reply-To: <200502041811.j14IBOna020338@ginger.cmf.nrl.navy.mil>
Hi,
chas williams - CONTRACTOR wrote:
> In message <20050121085123.GA2471@katya>,Roman Kagan writes:
>
>>The patch is against 2.6.10. Please comment.
>
>
> i guess i would prefer that entries be named typeN, like he0
> instead of just a number.
>
> you were printing 7 octets for the address.
>
> if !CONFIG_SYSFS, then __free_atm_dev() is going to need to do the
> kfree.
>
> i added some other fields that i think are interesting.
>
> comments?
>
> +
> +static ssize_t show_carrier(struct class_device *cdev, char *buf)
> +{
> + char *pos = buf;
> + struct atm_dev *adev = to_atm_dev(cdev);
> +
> + pos += sprintf(pos, "%d\n",
> + adev->signal == ATM_PHY_SIG_LOST ? 0 : 1);
> +
> + return pos - buf;
> +}
Shouldn't adev->signal == ATM_PHY_SIG_FOUND ? 1 : 0); be better : in the
case of ATM_PHY_SIG_UNKNOWN, it return 1...
Matthieu
next prev parent reply other threads:[~2005-02-04 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050119174543.GA2418@katya>
2005-01-21 8:51 ` [RFC][PATCH] Very basic sysfs support for ATM devices (updated) Roman Kagan
2005-02-04 18:11 ` [Linux-ATM-General] " chas williams - CONTRACTOR
2005-02-04 18:27 ` matthieu castet [this message]
2005-02-04 18:50 ` chas williams - CONTRACTOR
2005-02-04 20:13 ` Roman Kagan
2005-02-06 1:33 ` chas williams - CONTRACTOR
2005-02-06 19:19 ` Roman Kagan
2005-02-08 15:02 ` chas williams - CONTRACTOR
2005-02-08 16:45 ` Roman Kagan
2005-02-07 9:03 ` Duncan Sands
2005-02-07 9:45 ` Roman Kagan
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=4203BE7B.2030503@free.fr \
--to=castet.matthieu@free.fr \
--cc=chas@cmf.nrl.navy.mil \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=usbatm@lists.infradead.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).