From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Daniele Nicolodi <daniele@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Analogy: idx_write_subd field in a4l_desc_t
Date: Tue, 04 Oct 2011 13:17:58 +0200 [thread overview]
Message-ID: <4E8AEB66.9030500@domain.hid> (raw)
In-Reply-To: <4E8ABC9A.4070604@domain.hid>
On 10/04/2011 09:58 AM, Daniele Nicolodi wrote:
> On 01/10/11 20:07, Gilles Chanteperdrix wrote:
>>> For API / ABI compatibility reasons, I waited a major release before
>>> removing the fields idx_{read, write}_subd. I should have thought
>>> twice before removing their initializations. I will fix that soon,
>>> sorry.
>>
>> 2.6 is a new major release, and not out yet, so, if you want to remove
>> something, it is still time.
>
> If we are open to some partially backward incompatible changes I propose
> to also change the meaning of the a4l_desc_t board_name field, to really
> be the board name, instead of the driver name. I find this information
> more useful when enumerating devices in my setup.
>
> I would also like to propose a patch to demote some messages, logged at
> each interrupt, in the ni_pcimio driver from the info to the debug
> level. I run continuous acquisitions and those kernel messages pollute
> my syslog with not much added value and fill my disc with redundant
> information.
If you want things merged, send the patches, they will reach
xenomai-head repository through Alex.
--
Gilles.
next prev parent reply other threads:[~2011-10-04 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 14:06 [Xenomai-core] Analogy: idx_write_subd field in a4l_desc_t Daniele Nicolodi
2011-09-30 22:03 ` Alexis Berlemont
2011-10-01 18:07 ` Gilles Chanteperdrix
2011-10-04 7:58 ` Daniele Nicolodi
2011-10-04 11:17 ` Gilles Chanteperdrix [this message]
2011-10-04 13:31 ` Daniele Nicolodi
2011-10-05 21:53 ` Alexis Berlemont
2011-10-04 7:48 ` Daniele Nicolodi
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=4E8AEB66.9030500@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=daniele@domain.hid \
--cc=xenomai@xenomai.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.