From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Young <sean@mess.org>,
linux-media@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the v4l-dvb tree
Date: Sun, 5 Feb 2017 20:22:31 -0200 [thread overview]
Message-ID: <20170205202231.55ef80ff@vento.lan> (raw)
In-Reply-To: <20170206091914.56836dd3@canb.auug.org.au>
Em Mon, 6 Feb 2017 09:19:14 +1100
Stephen Rothwell <sfr@canb.auug.org.au> escreveu:
> Hi Mauro,
>
> On Thu, 2 Feb 2017 22:24:35 -0200 Mauro Carvalho Chehab <mchehab@osg.samsung.com> wrote:
> >
> > So, if this is not a problem to you, maybe you can setup your
> > environment to pull (in this order) from:
> >
> > git://linuxtv.org/media_tree.git fixes
> > git://linuxtv.org/media_tree.git master
> > git://linuxtv.org/mchehab/media-next.git master
> >
> > Most of the time, the last pull won't get anything.
>
> OK, from today I have those three trees called v4l-dvb-fixes, v4l-dvb
> and v4l-dvb-next respectively. We'll see how it goes.
OK!
Thanks!
Mauro
next parent reply other threads:[~2017-02-05 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170131115505.3f8c769b@canb.auug.org.au>
[not found] ` <20170203092446.7e86e8af@canb.auug.org.au>
[not found] ` <20170202204620.75b20605@vento.lan>
[not found] ` <20170203095934.2bbbbf45@canb.auug.org.au>
[not found] ` <20170202212440.5e514ebc@vento.lan>
[not found] ` <20170203110117.4a0c5628@canb.auug.org.au>
[not found] ` <20170202222435.2798402e@vento.lan>
[not found] ` <20170206091914.56836dd3@canb.auug.org.au>
2017-02-05 22:22 ` Mauro Carvalho Chehab [this message]
[not found] <20121112110935.eee5f582f16ab07c9faeabb1@canb.auug.org.au>
2012-11-13 13:14 ` linux-next: build failure after merge of the v4l-dvb tree Mauro Carvalho Chehab
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=20170205202231.55ef80ff@vento.lan \
--to=mchehab@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sean@mess.org \
--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 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).