From: christian pellegrin <chripell-VaTbYqLCNhc@public.gmane.org>
To: Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
Cc: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH net-next-2.6] can: Proper ctrlmode handling for CAN devices
Date: Thu, 14 Jan 2010 15:53:46 +0100 [thread overview]
Message-ID: <cabda6421001140653p296f4481oed1a1c731325961a@mail.gmail.com> (raw)
In-Reply-To: <4B4F2C01.5000007-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
On Thu, Jan 14, 2010 at 3:36 PM, Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org> wrote:
>
> I see. I really don't like the extra callback. Currently, it seems
> overkill to me. In principle, we could also do some checks in the device
> open function, if needed.
>
ack, I'll prepare a v2 patch soon.
>
> I found some links on that subject. Obviously, there is ENOTSUP and
> EOPNOTSUPP in the glibc, which are equal, but no ENOTSUPP. I tend to
> replace ENOTSUPP with EOPNOTSUPP, EINVAL or ENOSYS, what ever is more
> appropriate. Do you feel that EINVAL is more appropriate for the case above?
>
I'm perfectly ok with EOPNOTSUPP as you suggested.
--
Christian Pellegrin, see http://www.evolware.org/chri/
"Real Programmers don't play tennis, or any other sport which requires
you to change clothes. Mountain climbing is OK, and Real Programmers
wear their climbing boots to work in case a mountain should suddenly
spring up in the middle of the computer room."
prev parent reply other threads:[~2010-01-14 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 17:27 [PATCH net-next-2.6] can: Proper ctrlmode handling for CAN devices Christian Pellegrin
[not found] ` <1263403629-18827-1-git-send-email-chripell-VaTbYqLCNhc@public.gmane.org>
2010-01-13 19:56 ` Wolfgang Grandegger
[not found] ` <4B4E2567.8060907-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2010-01-14 14:18 ` christian pellegrin
[not found] ` <cabda6421001140618w2fb4e20fk680f8f01ff827e66-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-14 14:36 ` Wolfgang Grandegger
[not found] ` <4B4F2C01.5000007-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2010-01-14 14:53 ` christian pellegrin [this message]
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=cabda6421001140653p296f4481oed1a1c731325961a@mail.gmail.com \
--to=chripell-vatbyqlcnhc@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.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).