From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Archit Taneja <a0393947@ti.com>
Cc: "Hiremath, Vaibhav" <hvaibhav@ti.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [GIT PULL for v3.0] OMAP_VOUT bug fixes and code cleanup
Date: Fri, 01 Jul 2011 20:44:56 -0300 [thread overview]
Message-ID: <4E0E5BF8.8000707@redhat.com> (raw)
In-Reply-To: <4E0E4F14.1080007@ti.com>
Em 01-07-2011 19:49, Archit Taneja escreveu:
> Hi,
>
> On Friday 01 July 2011 11:48 AM, Mauro Carvalho Chehab wrote:
>> Em 22-06-2011 16:32, hvaibhav@ti.com escreveu:
>>> The following changes since commit af0d6a0a3a30946f7df69c764791f1b0643f7cd6:
>>> Linus Torvalds (1):
>>> Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/.../tip/linux-2.6-tip
>>>
>>> are available in the git repository at:
>>>
>>> git://arago-project.org/git/people/vaibhav/ti-psp-omap-video.git for-linux-media
>>>
>>
>>> Archit Taneja (3):
>>> OMAP_VOUT: CLEANUP: Move generic functions and macros to common files
>>> OMAP_VOUT: CLEANUP: Make rotation related helper functions more descriptive
>>> OMAP_VOUT: Create separate file for VRFB related API's
>>
>> Those are cleanup patches. NACK for 3.0. Cleanups should be sent to -next kernel (3.1).
>
> The first 2 patches are pre-requisite cleanup patches required for the 3rd patch. The third patch adds functionality, it prevents the driver using VRFB for OMAP4, and forces the use of SDMA buffers.
>
> So the patch set as a whole is not only cleanup, and I guess we could push it for 3.0.
Patches that add new functionalities shold also be delayed to -next. Only bug fixes
are allowed during the -rc cycle. Even patch 3 were a fix, you would need to rebase
it to not depend on the cleanups, for it to be accepted on a -rc kernel.
Regards,
Mauro
next prev parent reply other threads:[~2011-07-01 23:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 19:32 [GIT PULL for v3.0] OMAP_VOUT bug fixes and code cleanup hvaibhav
2011-07-01 18:43 ` Mauro Carvalho Chehab
2011-07-05 11:34 ` JAIN, AMBER
2011-07-06 20:43 ` David Rientjes
2011-07-07 5:55 ` Hiremath, Vaibhav
2011-07-07 5:57 ` JAIN, AMBER
2011-07-08 20:16 ` David Rientjes
2011-07-11 13:35 ` Hiremath, Vaibhav
2011-07-01 18:48 ` Mauro Carvalho Chehab
2011-07-01 22:49 ` Archit Taneja
2011-07-01 23:44 ` Mauro Carvalho Chehab [this message]
2011-07-02 1:31 ` Archit Taneja
2011-07-04 5:09 ` Hiremath, Vaibhav
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=4E0E5BF8.8000707@redhat.com \
--to=mchehab@redhat.com \
--cc=a0393947@ti.com \
--cc=hvaibhav@ti.com \
--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