All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Re: RT-Socket-CAN versioning
Date: Tue, 20 Feb 2007 00:36:21 +0100	[thread overview]
Message-ID: <45DA3475.5050500@domain.hid> (raw)
In-Reply-To: <17882.10993.117100.127933@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 2087 bytes --]

Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>  > Wolfgang Grandegger wrote:
>  > > Hi Jan,
>  > > 
>  > > currently the RT-Socket-CAN drivers maintains it's own version or
>  > > release number. As RT-Socket-CAN is part of Xenomai, I do not see the
>  > > need for it (and so far I did not update it). What is the intended use
>  > > of "driver_version" in "struct rtdm_device"?
>  > 
>  > Actually, I was thinking about this too yesterday. The idea of the
>  > separate versioning for RTDM drivers is to signal the users if something
>  > in the driver really changed. It's fairly obvious what to do with it for
>  > out-of-tree drivers, but for in-tree it might be worth considering the
>  > policy.
>  > 
>  > The current model, maintained more or less properly for the existing
>  > drivers, is to increment independently of Xenomai according to major or
>  > minor changes. One may ease this burden for the driver developer by
>  > simply filling in Xenomai's version here. That would just let the
>  > revisions increase on every Xenomai release, even if the driver remained
>  > untouched. The tag would still have a meaning for out-of-tree drivers,
>  > but for in-tree it would be fairly meaningless.
>  > 
>  > Well, whatever is commonly preferred, it should then be applied
>  > consistently on all RTDM drivers in Xenomai. What are the opinions on
>  > this list (I will comment afterwards)?
>  > 
>  > > Furthermore, there is also
>  > > "profile_version" (which does not show up n the Doxygen docu for some
>  > > strange reason).
>  > 
>  > The automatic update from the latest SVN must be broken on
>  > www.xenomai.org, there is more stuff missing.
> 
> The automatic update only updates the web site from the contents of the
> "generated" directory. In order to update this directory, go to the
> "doc" subdirectory of the build tree and type "make generate-doc", then
> run svn commit in the "generated" directory. I will install the proper
> version of doxygen and regenerate the documentation.
> 

Ah, thanks.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2007-02-19 23:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19 17:33 [Xenomai-core] RT-Socket-CAN versioning Wolfgang Grandegger
2007-02-19 17:59 ` [Xenomai-core] " Jan Kiszka
2007-02-19 22:55   ` Gilles Chanteperdrix
2007-02-19 23:36     ` Jan Kiszka [this message]
2007-02-24 21:34   ` Wolfgang Grandegger
2007-02-25 10:02     ` Jan Kiszka

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=45DA3475.5050500@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.