From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, linux-next@vger.kernel.org
Subject: Re: linux-next: no tree for Sept 6
Date: Wed, 21 Sep 2011 23:48:45 -0300 [thread overview]
Message-ID: <4E7AA20D.2000605@infradead.org> (raw)
In-Reply-To: <20110922122352.61843f389e78c6ffde0a703b@canb.auug.org.au>
Em 21-09-2011 23:23, Stephen Rothwell escreveu:
> Hi Mauro,
>
> On Wed, 21 Sep 2011 22:54:12 -0300 Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
>>
>> Hi Stephen,
>>
>> Please replace my media tree (v4l-dvb) by this one:
>> git://linuxtv.org/mchehab/media-next.git
>
> I have switched to this from today.
Thank you!
>> I'll set soon a new tree for my edac patches as well.
>
> OK
>
Ok, just set a git tree for the edac drivers I'm maintaining.
It is at:
git://git.infradead.org/users/mchehab/edac.git
It replaces both my old i7core and edac trees.
Could you please replace it for the linux-next builds?
It contains the fix for the compilation error on i386, as reported by Randy.
Thanks!
Mauro
next prev parent reply other threads:[~2011-09-22 2:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 6:40 linux-next: no tree for Sept 6 Stephen Rothwell
2011-09-06 17:17 ` Arnaud Lacombe
2011-09-06 17:23 ` Josh Boyer
2011-09-06 17:29 ` Arnaud Lacombe
2011-09-06 17:37 ` Randy Dunlap
2011-09-06 18:18 ` Josh Boyer
2011-09-06 18:30 ` Arnaud Lacombe
2011-09-07 14:08 ` Mauro Carvalho Chehab
2011-09-11 4:19 ` Stephen Rothwell
2011-09-22 1:54 ` Mauro Carvalho Chehab
2011-09-22 2:23 ` Stephen Rothwell
2011-09-22 2:48 ` Mauro Carvalho Chehab [this message]
2011-09-22 14:26 ` Stephen Rothwell
2011-09-22 17:48 ` Mauro Carvalho Chehab
2011-09-07 7:16 ` Stephen Rothwell
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=4E7AA20D.2000605@infradead.org \
--to=mchehab@infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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.