From: mchehab@redhat.com (Mauro Carvalho Chehab)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] davinci: dm646x: move vpif related code to driver core header from platform
Date: Thu, 24 Nov 2011 16:05:24 -0200 [thread overview]
Message-ID: <4ECE8764.60800@redhat.com> (raw)
In-Reply-To: <1321110362-6699-1-git-send-email-manjunath.hadli@ti.com>
Em 12-11-2011 13:06, Manjunath Hadli escreveu:
> move vpif related code for capture and display drivers
> from dm646x platform header file to vpif_types.h as these definitions
> are related to driver code more than the platform or board.
>
> Signed-off-by: Manjunath Hadli <manjunath.hadli@ti.com>
Manju,
Why are you re-sending a patch?
My understanding is that you're maintaining the davinci patches, so it is
up to you to put those patches on your tree and send me a pull request when
they're done. So, please, don't pollute the ML re-sending emails that
are for yourself to handle.
Regards,
Mauro.
next prev parent reply other threads:[~2011-11-24 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 15:06 [PATCH RESEND] davinci: dm646x: move vpif related code to driver core header from platform Manjunath Hadli
2011-11-24 18:05 ` Mauro Carvalho Chehab [this message]
2011-11-24 18:22 ` Nori, Sekhar
2011-11-24 20:06 ` Mauro Carvalho Chehab
2011-11-30 10:47 ` Nori, Sekhar
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=4ECE8764.60800@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).