From: Thomas Chou <thomas@wytron.com.tw>
To: Jonas Bonn <jonas@southpole.se>
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 22:50:57 +0800 [thread overview]
Message-ID: <4D3D91D1.8000701@wytron.com.tw> (raw)
In-Reply-To: <1295866794.23825.100.camel@needafix>
Hi Jonas,
On 01/24/2011 06:59 PM, Jonas Bonn wrote:
> 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.
I will follow your suggestion exactly. Thank you very much.
Best regards,
Thomas
next prev parent reply other threads:[~2011-01-25 0:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1294645208-6322-1-git-send-email-thomas@wytron.com.tw>
2011-01-12 2:41 ` [PATCH v2] spi: add OpenCores tiny SPI driver Thomas Chou
2011-01-17 7:32 ` Thomas Chou
2011-01-20 16:54 ` Grant Likely
2011-01-20 21:36 ` Thomas Chou
2011-01-21 12:27 ` Jonas Bonn
2011-01-24 1:19 ` Thomas Chou
2011-01-24 10:59 ` Jonas Bonn
2011-01-24 14:50 ` Thomas Chou [this message]
2011-01-24 15:50 ` Grant Likely
2011-01-25 3:17 ` [PATCH v3] " Thomas Chou
2011-02-03 10:37 ` [PATCH v4] " 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=4D3D91D1.8000701@wytron.com.tw \
--to=thomas@wytron.com.tw \
--cc=dbrownell@users.sourceforge.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=nios2-dev@sopc.et.ntust.edu.tw \
--cc=spi-devel-general@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox