From: "Richard Röjfors" <richard.rojfors@pelagicore.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Douglas Schilling Landgraf <dougsland@gmail.com>,
p.osciak@samsung.com
Subject: [PATCH 0/2 v3] media, mfd: Add timberdale video-in driver
Date: Mon, 09 Aug 2010 16:35:14 +0200 [thread overview]
Message-ID: <1281364514.5762.28.camel@debian> (raw)
To follow are three patches.
Since last patch I removed the uncached buffers patch, it
needs to be investigated further.
The first adds the timberdale video-in driver to the media tree.
The second adds it to the timberdale MFD driver.
Samuel and Mauro hope you can support and solve the potential merge
issue between your two trees.
Thanks
--Richard
next reply other threads:[~2010-08-09 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 14:35 Richard Röjfors [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-25 14:40 [PATCH 0/2 v3] media, mfd: Add timberdale video-in driver Richard Röjfors
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=1281364514.5762.28.camel@debian \
--to=richard.rojfors@pelagicore.com \
--cc=dougsland@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=p.osciak@samsung.com \
--cc=sameo@linux.intel.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