From: Arnd Bergmann <arnd@arndb.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Jamie Iles <jamie@jamieiles.com>,
linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [RFC PATCHv2 1/4] drivers/otp: add initial support for OTP memory
Date: Sat, 26 Mar 2011 21:51:46 +0100 [thread overview]
Message-ID: <201103262151.47061.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTik7qzFC_WQPrJAMbV0b6-+CTNfP6CcQnK6BKiWn@mail.gmail.com>
On Saturday 26 March 2011 18:55:39 Mike Frysinger wrote:
> >> i would add an ABI field here too so if in the future we want to add
> >> stuff, we can do so without adding new ioctls. like "u16 version; u16
> >> flags;". then in the ioctl, if version isnt 0, we return ENOTSUP. in
> >> the future, we can add flags or bump the version.
> >
> > No, versioned APIs are just a pain to maintain, it's easier to add
> > new ioctl commands when necessary.
> > Note that the kernel would always have to support all versions of
> > the API anyway.
>
> adding at least a flags field then should be fine
Fine with me, if you can name at least one possible use for a flag.
I think it would be better without a flags field, but it's not a
problem if you insist on having it.
Arnd
next prev parent reply other threads:[~2011-03-26 20:51 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 15:21 [RFC PATCHv2 0/4] Support for OTP memory Jamie Iles
2011-03-24 15:21 ` [RFC PATCHv2 1/4] drivers/otp: add initial support " Jamie Iles
2011-03-24 18:32 ` Mike Frysinger
2011-03-24 20:35 ` Jamie Iles
2011-03-24 21:33 ` Mike Frysinger
2011-03-25 10:08 ` Jamie Iles
2011-03-25 21:32 ` Mike Frysinger
2011-03-25 22:27 ` Jamie Iles
2011-03-25 22:36 ` Mike Frysinger
2011-03-24 19:20 ` Greg KH
2011-03-24 20:49 ` Jamie Iles
2011-03-25 20:12 ` Arnd Bergmann
2011-03-25 21:12 ` Greg KH
2011-03-25 22:01 ` Arnd Bergmann
2011-03-25 23:28 ` Greg KH
2011-03-26 11:25 ` Arnd Bergmann
2011-03-26 15:10 ` Greg KH
2011-03-28 13:11 ` Arnd Bergmann
2011-03-25 22:23 ` Jamie Iles
2011-03-25 22:35 ` Arnd Bergmann
2011-03-25 22:38 ` Mike Frysinger
2011-03-25 22:52 ` Jamie Iles
2011-03-25 23:02 ` Arnd Bergmann
2011-03-26 0:21 ` Jamie Iles
2011-03-26 2:16 ` Mike Frysinger
2011-03-26 2:40 ` Jamie Iles
2011-03-26 10:54 ` Arnd Bergmann
2011-03-26 17:55 ` Mike Frysinger
2011-03-26 20:51 ` Arnd Bergmann [this message]
2011-03-27 3:52 ` Mike Frysinger
2011-03-27 11:18 ` Arnd Bergmann
2011-03-25 22:53 ` Arnd Bergmann
2011-03-24 15:21 ` [RFC PATCHv2 2/4] drivers/otp: add support for Picoxcell PC3X3 OTP Jamie Iles
2011-03-24 18:50 ` Mike Frysinger
2011-03-24 20:59 ` Jamie Iles
2011-03-24 21:40 ` Mike Frysinger
2011-03-24 15:21 ` [RFC PATCHv2 3/4] drivers/otp: allow an ioctl to be specified Jamie Iles
2011-03-24 18:35 ` Mike Frysinger
2011-03-24 20:36 ` Jamie Iles
2011-03-24 15:21 ` [RFC PATCHv2 4/4] drivers/otp: convert bfin otp to generic OTP Jamie Iles
2011-03-24 18:52 ` Mike Frysinger
2011-03-24 20:40 ` Jamie Iles
2011-03-24 17:39 ` [RFC PATCHv2 0/4] Support for OTP memory Mike Frysinger
2011-03-24 17:47 ` Jamie Iles
2011-03-24 17:56 ` Mike Frysinger
2011-03-24 18:32 ` Jamie Iles
2011-03-24 18:36 ` Mike Frysinger
2011-03-24 20:38 ` Jamie Iles
2011-03-25 0:12 ` Mark Brown
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=201103262151.47061.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=gregkh@suse.de \
--cc=jamie@jamieiles.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier@gentoo.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 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.