From: Randy Dunlap <rdunlap@infradead.org>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Hans Verkuil <hverkuil@xs4all.nl>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] usbtv: fix dependency
Date: Wed, 03 Jul 2013 10:26:20 -0700 [thread overview]
Message-ID: <51D45EBC.5050906@infradead.org> (raw)
In-Reply-To: <20130628145458.271fd9d8.mchehab@redhat.com>
On 06/28/13 10:54, Mauro Carvalho Chehab wrote:
> Em Fri, 28 Jun 2013 10:55:15 -0300
> Mauro Carvalho Chehab <mchehab@redhat.com> escreveu:
>
>>> This patch
>>>
>>> http://git.linuxtv.org/gliakhovetski/v4l-dvb.git/commitdiff/a92d0222c693db29a5d00eaedcdebf748789c38e
>>>
>>> has been pushed 3 days ago:
>>>
>>> https://patchwork.linuxtv.org/patch/19090/
>>
>> As, according with:
>> https://lwn.net/Articles/556034/rss
>>
>> -rc7 is likely the last one before 3.10, that means that the media merge
>> window for 3.11 is closed already (as we close it one week before, in order
>> to give more time for reviewing the patches better at -next).
>>
>> So, please split the fix patches from it on a separate pull request.
>
> Hmm... just took a look at the actual pull request... from the description,
> it seems to contain just fixes/documentation, so, I'll be handling it
> in a few.
Has this patch been merged yet? If so, where?
This build failure is still occurring in linux-next-20130703.
thanks,
--
~Randy
prev parent reply other threads:[~2013-07-03 17:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 8:24 [PATCH] usbtv: fix dependency Hans Verkuil
2013-06-28 11:00 ` Mauro Carvalho Chehab
2013-06-28 11:18 ` Hans Verkuil
2013-06-28 12:42 ` Mauro Carvalho Chehab
2013-06-28 12:59 ` Hans Verkuil
2013-06-28 13:24 ` Guennadi Liakhovetski
2013-06-28 13:55 ` Mauro Carvalho Chehab
2013-06-28 14:15 ` Hans Verkuil
2013-06-28 15:32 ` Mauro Carvalho Chehab
2013-06-28 17:54 ` Mauro Carvalho Chehab
2013-07-03 17:26 ` Randy Dunlap [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=51D45EBC.5050906@infradead.org \
--to=rdunlap@infradead.org \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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