All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Bonn <jonas-A9uVI2HLR7kOP4wsBPIw7w@public.gmane.org>
To: Thomas Chou <thomas-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
Cc: nios2-dev-1eJk0qcHJCcaeqlQEoCUNoJY59XmG8rH@public.gmane.org,
	David Brownell
	<dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH v2] spi: add OpenCores tiny SPI driver
Date: Mon, 24 Jan 2011 11:59:54 +0100	[thread overview]
Message-ID: <1295866794.23825.100.camel@needafix> (raw)
In-Reply-To: <4D3CD38D.4080808-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>

Hi Thomas,

> > Versioning of OpenCores cores is not sorted yet.  In order to avoid
> > clashing with the versioning/naming scheme that's decided on, please
> > just use a neutral version number for now (especially as your core is so
> > new).  e.g. "opencores,tiny-spi-0"
> >
> 
> Thanks. I will update it to "opencores,tiny-spi-1.0".
> 

We've discussed this a bit internally now and decided that the best way
to version OpenCores cores is to use the SVN commit ID of the rtl/
directory in the project's repository.  So, for your tiny-spi project,
the last SVN commit to update the rtl/ directory was commit number 2;
hence, I'd recommend you use the following device tree identifier:

opencores,tiny-spi-rtlsvn2

That's:  opencores,<project>-rtl<VCS><commit ID>

As projects are currently in SVN, VCS=svn.

Linux drivers for other OpenCores cores will be updated accordingly.

/Jonas


------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d

WARNING: multiple messages have this Message-ID (diff)
From: Jonas Bonn <jonas@southpole.se>
To: Thomas Chou <thomas@wytron.com.tw>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	nios2-dev@sopc.et.ntust.edu.tw,
	David Brownell <dbrownell@users.sourceforge.net>,
	Mike Frysinger <vapier@gentoo.org>,
	devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org,
	spi-devel-general@lists.sourceforge.net
Subject: Re: [PATCH v2] spi: add OpenCores tiny SPI driver
Date: Mon, 24 Jan 2011 11:59:54 +0100	[thread overview]
Message-ID: <1295866794.23825.100.camel@needafix> (raw)
In-Reply-To: <4D3CD38D.4080808@wytron.com.tw>

Hi Thomas,

> > Versioning of OpenCores cores is not sorted yet.  In order to avoid
> > clashing with the versioning/naming scheme that's decided on, please
> > just use a neutral version number for now (especially as your core is so
> > new).  e.g. "opencores,tiny-spi-0"
> >
> 
> Thanks. I will update it to "opencores,tiny-spi-1.0".
> 

We've discussed this a bit internally now and decided that the best way
to version OpenCores cores is to use the SVN commit ID of the rtl/
directory in the project's repository.  So, for your tiny-spi project,
the last SVN commit to update the rtl/ directory was commit number 2;
hence, I'd recommend you use the following device tree identifier:

opencores,tiny-spi-rtlsvn2

That's:  opencores,<project>-rtl<VCS><commit ID>

As projects are currently in SVN, VCS=svn.

Linux drivers for other OpenCores cores will be updated accordingly.

/Jonas


  parent reply	other threads:[~2011-01-24 10:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1294645208-6322-1-git-send-email-thomas@wytron.com.tw>
     [not found] ` <1294645208-6322-1-git-send-email-thomas-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
2011-01-12  2:41   ` [PATCH v2] spi: add OpenCores tiny SPI driver Thomas Chou
2011-01-12  2:41     ` Thomas Chou
     [not found]     ` <1294800109-31603-1-git-send-email-thomas-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
2011-01-17  7:32       ` Thomas Chou
2011-01-17  7:32         ` Thomas Chou
     [not found]         ` <1295249542-26743-1-git-send-email-thomas-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
2011-01-20 16:54           ` Grant Likely
2011-01-20 16:54             ` Grant Likely
2011-01-20 21:36             ` Thomas Chou
     [not found]               ` <4D38AAEB.7020308-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
2011-01-21 12:27                 ` Jonas Bonn
2011-01-21 12:27                   ` Jonas Bonn
2011-01-24  1:19                   ` Thomas Chou
2011-01-24  1:19                     ` Thomas Chou
     [not found]                     ` <4D3CD38D.4080808-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
2011-01-24 10:59                       ` Jonas Bonn [this message]
2011-01-24 10:59                         ` Jonas Bonn
2011-01-24 14:50                         ` Thomas Chou
2011-01-24 14:50                           ` Thomas Chou
     [not found]                           ` <4D3D91D1.8000701-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
2011-01-24 15:50                             ` Grant Likely
2011-01-24 15:50                               ` Grant Likely
2011-01-25  3:17                         ` [PATCH v3] " Thomas Chou
2011-01-25  3:17                           ` Thomas Chou
     [not found]                           ` <1295925450-28550-1-git-send-email-thomas-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
2011-02-03 10:37                             ` [PATCH v4] " Thomas Chou
2011-02-03 10:37                               ` Thomas Chou
2011-02-03 11:03                               ` Wolfram Sang
2011-02-03 15:20                               ` Dirk Brandewie

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=1295866794.23825.100.camel@needafix \
    --to=jonas-a9uvi2hlr7kop4wsbpiw7w@public.gmane.org \
    --cc=dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=nios2-dev-1eJk0qcHJCcaeqlQEoCUNoJY59XmG8rH@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=thomas-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org \
    --cc=vapier-aBrp7R+bbdUdnm+yROfE0A@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 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.