From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: backports@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [PATCH 6/7] backports: add media subsystem drivers
Date: Sat, 13 Apr 2013 23:02:41 +0200 [thread overview]
Message-ID: <1365886961.1089.6.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1365862424-6530-7-git-send-email-mcgrof@do-not-panic.com> (sfid-20130413_161421_323308_27727044)
On Sat, 2013-04-13 at 07:13 -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
>
> This adds backport support for all media subsystem
> drivers. This is enabled only for >= 3.2. Some media
> drivers rely on the new probe deferrral mechanism
> (-EPROBE_DEFER see commit d1c3414c), those are only
> enabled for kernels >= 3.4. Some media drivers only
> depend on the regulatory but since we only support
> backporting the regulatory on kernels >= 3.4 we only
> enable those media drivers for >= 3.4.
>
> This backports 433 media drivers.
Heh. Applied. Good thing I can kill the pr_fmt patches again soon.
johannes
prev parent reply other threads:[~2013-04-13 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1365862424-6530-1-git-send-email-mcgrof@do-not-panic.com>
2013-04-13 14:13 ` [PATCH 5/7] backports: add support for voltage / current regulator drivers Luis R. Rodriguez
2013-04-13 21:01 ` Johannes Berg
2013-04-15 16:26 ` Mark Brown
2013-04-15 16:33 ` Johannes Berg
2013-04-22 13:11 ` Mark Brown
2013-04-23 6:18 ` Luis R. Rodriguez
2013-04-15 16:25 ` Mark Brown
2013-04-13 14:13 ` [PATCH 6/7] backports: add media subsystem drivers Luis R. Rodriguez
2013-04-13 21:02 ` Johannes Berg [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=1365886961.1089.6.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mchehab@redhat.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
Powered by JetHome