From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Adrian Bunk <bunk@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
v4l-dvb-maintainer@linuxtv.org, video4linux-list@redhat.com,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: v4l/mips build problem
Date: Tue, 5 Aug 2008 13:19:42 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808051315440.22576@bombadil.infradead.org> (raw)
In-Reply-To: <20080806023906.c2f919b4.sfr@canb.auug.org.au>
On Wed, 6 Aug 2008, Stephen Rothwell wrote:
> Hi Andrew,
>
> On Tue, 5 Aug 2008 09:26:50 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>> yup, I'll send it in unless it turned up in today's linux-next.
>
> Which I think is unlikely: the v4l/dvb tree has been unmergable since
> 29/7 and I haven't heard from Mauro since then.
Too busy during those days. I don't mind if Andrew prefer to forward this
directly, but I have another bunch of patches to send Linus probably
today.
I did some changes on the procedures I use for sending patches upstream,
but I want to do some additional tests here to be sure that everything is
all right. The idea is never rebase my main branches again.
--
Cheers,
Mauro Carvalho Chehab
http://linuxtv.org
mchehab@infradead.org
prev parent reply other threads:[~2008-08-05 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 15:23 Stephen Rothwell
2008-08-05 15:41 ` Adrian Bunk
2008-08-05 16:06 ` Stephen Rothwell
2008-08-05 16:26 ` Andrew Morton
2008-08-05 16:39 ` Stephen Rothwell
2008-08-05 17:19 ` Mauro Carvalho Chehab [this message]
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=alpine.LFD.1.10.0808051315440.22576@bombadil.infradead.org \
--to=mchehab@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=video4linux-list@redhat.com \
/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
all inboxes | Powered by JetHome®