From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: video_device -> v4l2_devnode rename
Date: Wed, 19 Jan 2011 08:59:24 -0200 [thread overview]
Message-ID: <4D36C40C.3080607@redhat.com> (raw)
In-Reply-To: <201101190839.15175.hverkuil@xs4all.nl>
Em 19-01-2011 05:39, Hans Verkuil escreveu:
> Hi Mauro,
>
> I saw that 2.6.38-rc1 was released. I also noticed that not all the patches
> that are in the for_2.6.38-rc1 branch are in 2.6.38-rc1.
Yes. Unfortunately, when I was sending the pull request yesterday, I noticed
an issue on my linux next tree, and I had to abort its send. After that, Linus
released -rc1, before I have time to fix it.
People should really send me patches for the next window before the start of the
merge window, as doing it during the merge window makes my work harder and may
cause troubles like that.
The net result is that most patches were submitted in time and were applied upstream.
Of course, there are usual fix patches sent during the merge window, that will be sent
upstream anyway during the rc period.
There are two patch series with new stuff submitted in time and merged on my
tree that didn't reach upstream:
- vb2/s5p-fimc - they required me more time to review - I also spent 3 days testing it;
- ngene - there were a pending API discussion - I waited for a while to see if
there were some solution, before deciding to merge and move the problematic
code to staging.
So, I'll need to dig into the pending patches, in order to send the ones that
are acceptable after the end of the merge window, and letting the other patches
for .39. I'll likely try to send the two above and the dib0700 patches on a separate
pull request, but this pull request might be rejected.
> We want to rename video_device to v4l2_devnode. So let me know when I can
> finalize my patches and, most importantly, against which branch.
It is too late for that. As I said you, the better time for doing that is during
the merge window. Linus said me that he don't want to make life easier for function
rename. So, he won't be accepting such patch after the merge window.
Cheers,
Mauro
next prev parent reply other threads:[~2011-01-19 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 7:39 video_device -> v4l2_devnode rename Hans Verkuil
2011-01-19 10:59 ` Mauro Carvalho Chehab [this message]
2011-01-19 11:53 ` Hans Verkuil
2011-01-19 12:02 ` Mauro Carvalho Chehab
2011-01-19 11:26 ` Mauro Carvalho Chehab
2011-01-19 11:59 ` Hans Verkuil
2011-01-19 12:17 ` 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=4D36C40C.3080607@redhat.com \
--to=mchehab@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.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