From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Richard Zhao <richard.zhao@freescale.com>
Cc: "javier Martin" <javier.martin@vista-silicon.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Mauro Carvalho Chehab" <mchehab@infradead.org>,
linux-media@vger.kernel.org,
"Ezequiel García" <elezegarcia@gmail.com>
Subject: Re: [GIT PULL v2] Initial i.MX5/CODA7 support for the CODA driver
Date: Thu, 20 Sep 2012 10:34:08 +0200 [thread overview]
Message-ID: <505AD500.3040408@samsung.com> (raw)
In-Reply-To: <20120920080358.GB9407@b20223-02.ap.freescale.net>
On 09/20/2012 10:03 AM, Richard Zhao wrote:
> On Thu, Sep 20, 2012 at 09:10:46AM +0200, javier Martin wrote:
>> Hi Richard,
>>
>> On 20 September 2012 05:32, Richard Zhao <richard.zhao@freescale.com> wrote:
>>> why is it a request-pull?
>>
>> After 5 version of Philipp's patches we have agreed they are good
>> enough to be merged; they don't break anything related to the old
>> codadx6 while provide support for the new coda7:
>> http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/53627
>>
>> The pull request is a way to tell Mauro this is ready to be merged in
>> his linux-media tree and making things easier for him.
> I know the meaning. I just feel strange. Pull request is normally sent
> by maintainer to up level maintainer who agreed to receive pull request.
There is really high volume of various kind of patches on linux-media
mailing lists. Even with those pull requests it becomes hard for Mauro
to respond and merge patches in timely manner. There is even a discussion
related to this scheduled for media workshop during ELCE/LinuxCon. I think
the rules may differ slightly across kernel subsystems, hence I find nothing
unusual in using pull requests, especially by sub-subsystem maintainers or
developers.
Regards,
Sylwester
prev parent reply other threads:[~2012-09-20 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 8:46 [GIT PULL v2] Initial i.MX5/CODA7 support for the CODA driver Philipp Zabel
2012-09-20 3:32 ` Richard Zhao
2012-09-20 7:10 ` javier Martin
2012-09-20 8:03 ` Richard Zhao
2012-09-20 8:33 ` javier Martin
2012-09-20 8:34 ` Sylwester Nawrocki [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=505AD500.3040408@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=elezegarcia@gmail.com \
--cc=javier.martin@vista-silicon.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=richard.zhao@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.