From: Alexis RODET <alexis.rodet@bvs-tech.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: David Brownell <david-b@pacbell.net>,
spi-devel-general@lists.sourceforge.net,
Baruch Siach <baruch@tkos.co.il>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/1] Renaming 'struct flash_platform_data' into 'struct spi_flash_platform_data' in include/linux/spi/flash.h
Date: Tue, 25 Jan 2011 10:40:49 +0100 [thread overview]
Message-ID: <4D3E9AA1.4020308@bvs-tech.com> (raw)
In-Reply-To: <AANLkTikDHbKt5q+o2LK89hHZ3EUeeYzmQVJj8jXgQ+pB@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
Hello,
Le 24/01/2011 18:52, Grant Likely a écrit :
> On Mon, Jan 24, 2011 at 8:49 AM, Alexis RODET <alexis.rodet@bvs-tech.com> wrote:
>> Hi again,
>>
>> In facts I don't know which git URL to clone for getting linux-next as patch base, can you tell me ?
>> I'm working on last stable release from git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6-stable.git.
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>
> Be warned, it is rebased every night.
>
It seems to have been frozen for 4 days and to have become late behind git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Alexis
[-- Attachment #2: alexis_rodet.vcf --]
[-- Type: text/x-vcard, Size: 316 bytes --]
begin:vcard
fn:Alexis RODET
n:RODET;Alexis
org:Brain Vision Systems
adr:;;32 rue du Javelot;PARIS;;75013;FRANCE
email;internet:alexis.rodet@bvs-tech.com
title:Hardware Engineer
tel;work:+33 9 53 92 14 41
tel;fax:+33 9 58 92 14 41
x-mozilla-html:FALSE
url:http://www.bvs-tech.com
version:2.1
end:vcard
next prev parent reply other threads:[~2011-01-25 9:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101117160514.GA5308@n2100.arm.linux.org.uk>
2010-11-18 9:34 ` [PATCH] Renaming 'struct flash_platform_data' into 'struct spi_flash_platform_data' in include/linux/spi/flash.h Alexis RODET
2010-11-18 9:34 ` [PATCH] Renaming 'struct flash_platform_data' into 'struct Alexis RODET
[not found] ` <4CE6B27D.2000909@bvs-tech.com>
[not found] ` <20101121044720.GA6088@tarshish>
2010-11-22 9:58 ` [PATCH] Renaming 'struct flash_platform_data' into 'struct spi_flash_platform_data' in include/linux/spi/flash.h Alexis RODET
2010-11-22 13:59 ` David Brownell
2010-11-22 14:15 ` Alexis RODET
2010-11-22 21:52 ` David Brownell
2010-11-23 9:30 ` Alexis RODET
2010-11-23 9:36 ` Baruch Siach
2010-11-23 9:41 ` Alexis RODET
2010-11-23 9:44 ` Baruch Siach
2010-11-23 9:55 ` Alexis RODET
2011-01-21 19:28 ` Grant Likely
2011-01-24 11:37 ` [PATCH 0/1] " Alexis RODET
2011-01-24 15:16 ` [PATCH 1/1] " Alexis RODET
2011-01-24 15:49 ` [PATCH 0/1] " Alexis RODET
2011-01-24 17:52 ` Grant Likely
2011-01-25 9:23 ` Alexis RODET
2011-01-31 11:29 ` [PATCH 1/1] merging arch/arm/include/asm/mach/flash.h and include/linux/spi/flash.h into single header file include/linux/mtd/flash.h Alexis RODET
2011-07-10 7:38 ` Grant Likely
2011-01-25 9:40 ` Alexis RODET [this message]
2011-01-26 14:35 ` [PATCH 0/1] Renaming 'struct flash_platform_data' into 'struct spi_flash_platform_data' in include/linux/spi/flash.h Josh Boyer
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=4D3E9AA1.4020308@bvs-tech.com \
--to=alexis.rodet@bvs-tech.com \
--cc=baruch@tkos.co.il \
--cc=david-b@pacbell.net \
--cc=dwmw2@infradead.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-mtd@lists.infradead.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).