From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Pawel Osciak <p.osciak@samsung.com>,
linux-media@vger.kernel.org, m.szyprowski@samsung.com,
kyungmin.park@samsung.com
Subject: Re: [PATCH v2] v4l: videobuf: code cleanup.
Date: Wed, 17 Mar 2010 18:03:20 -0300 [thread overview]
Message-ID: <4BA14398.70609@redhat.com> (raw)
In-Reply-To: <201003172134.47721.hverkuil@xs4all.nl>
Hans Verkuil wrote:
> On Wednesday 17 March 2010 14:04:21 Pawel Osciak wrote:
>> Make videobuf pass checkpatch; minor code cleanups.
>>
>> Signed-off-by: Pawel Osciak <p.osciak@samsung.com>
>> Reviewed-by: Kyungmin Park <kyungmin.park@samsung.com>
>
> Reviewed-by: Hans Verkuil <hverkuil@xs4all.nl>
>
> It would be really nice if this can be merged soon. With all the work that
> we want to do on videobuf it makes life easier if it is cleaned up first.
>
> I wonder if it is perhaps possible to get this merged for 2.6.34-rc2?
> That way it will be easier to merge fixes there. Although I think that it
> is unlikely that we will want to make any videobuf changes for 2.6.34.
Videobuf changes for 2.6.34? Only if you catch a bug that affect the current
drivers and after lots of testing. It seems very unlikely. I don't see any
reason to send a pure cleanup patch outside the merge window. So, after review,
I'll add it at v4l-dvb.git tree (so, a patch for 2.6.35).
--
Cheers,
Mauro
prev parent reply other threads:[~2010-03-17 21:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 13:04 Pawel Osciak
2010-03-17 13:04 ` [PATCH v2] v4l: videobuf: code cleanup Pawel Osciak
2010-03-17 14:08 ` Aguirre, Sergio
2010-03-17 14:15 ` Pawel Osciak
2010-03-17 14:29 ` Hans Verkuil
2010-03-17 14:34 ` Aguirre, Sergio
2010-03-17 14:43 ` Pawel Osciak
2010-03-17 19:42 ` Mauro Carvalho Chehab
2010-03-24 14:54 ` Mauro Carvalho Chehab
2010-03-24 15:49 ` Hans Verkuil
2010-03-17 14:26 ` Hans Verkuil
2010-03-17 14:32 ` Aguirre, Sergio
2010-03-17 20:34 ` Hans Verkuil
2010-03-17 21:03 ` 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=4BA14398.70609@redhat.com \
--to=mchehab@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=p.osciak@samsung.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