From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: v4l-dvb tree
Date: Wed, 17 Dec 2008 14:01:50 +1100 [thread overview]
Message-ID: <20081217140150.b9c03f32.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20081217001818.7ad1c476@caramujo.chehab.org>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
Hi Mauro,
On Wed, 17 Dec 2008 00:18:18 -0200 Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
>
> I got the error. My update scripts weren't adding the patches at the right
> branch. I fixed the scripts and checked it on master.kernel.org.
>
> Now, you should be seen this changeset:
> 53e66c026200c8de67bf188bddc6c25d78dc8809
I do now, thanks. I will readd the v4l-dvb tree at the end of today's
linux-next.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-12-17 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 5:57 linux-next: v4l-dvb tree Stephen Rothwell
2008-12-16 19:36 ` Mauro Carvalho Chehab
2008-12-17 0:10 ` Stephen Rothwell
2008-12-17 2:18 ` Mauro Carvalho Chehab
2008-12-17 3:01 ` Stephen Rothwell [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=20081217140150.b9c03f32.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@infradead.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