From: Hans Verkuil <hverkuil@xs4all.nl>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH RFC 00/10] media file tree reorg - part 1
Date: Fri, 15 Jun 2012 09:39:28 +0200 [thread overview]
Message-ID: <4FDAE6B0.5020301@xs4all.nl> (raw)
In-Reply-To: <1339706161-22713-1-git-send-email-mchehab@redhat.com>
On 14/06/12 22:35, Mauro Carvalho Chehab wrote:
> As discussed a while ago, breaking media drivers by V4L or DVB
> is confusing, as:
> - hybrid devices are at V4L drivers;
> - DVB-only devices for chips that support analog are at
> V4L drivers;
> - Analog support addition on a DVB driver would require it
> to move to V4L drivers.
>
> Instead, move all drivers into a per-bus directory, and common drivers
> used by more than one driver into /common.
>
> This is the part 1 of this idea: it moves the core drivers to
> /drivers/media/foo-core, and re-arranges the DVB files.
>
> After this patch series, the directory structure will be:
>
> drivers/media/
> |-- common
> | `--<common drivers>
> |-- dvb-core
> |-- dvb-frontends
> |-- firewire
> |-- mmc
> | `--<mmc/sdio drivers>
> |-- pci
> | `--<pci/pcie drivers>
> |-- radio
> | `--<radio drivers>
> |-- rc
> | `-- keymaps
> |-- tuners
> |-- usb
> | `--<usb drivers>
> |-- v4l2-core
> `-- video
>
> PS.: The "video" directory is currently unchanged. It currently
> contains subdevs, common V4L drivers, and V4L bridges.
>
> On this series, I avoided mixing the file tree reorganization with
> menu improvements. Those will happen together with the second part,
> when the devices under video will be moved to /common, /usb, /pci...
> dirs.
Looks good to me. I like that saa7146 gets its own directory :-)
One request: before you commit this, can you go through the pending
patches for 3.6 and apply all the non-controversial ones? Otherwise
everyone will have to rebase their work.
Regards,
Hans
next prev parent reply other threads:[~2012-06-15 7:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 20:35 [PATCH RFC 00/10] media file tree reorg - part 1 Mauro Carvalho Chehab
2012-06-14 20:35 ` [PATCH RFC 01/10] [media] v4l: move v4l2 core into a separate directory Mauro Carvalho Chehab
2012-06-14 20:35 ` [PATCH RFC 02/10] [media] dvb: move the dvb core one level up Mauro Carvalho Chehab
2012-06-14 20:35 ` [PATCH RFC 03/10] [media] move the dvb/frontends to drivers/media/dvb-frontends Mauro Carvalho Chehab
2012-06-14 20:35 ` [PATCH RFC 04/10] [media] firewire: move it one level up Mauro Carvalho Chehab
2012-06-14 20:35 ` [PATCH RFC 05/10] [media] dvb-usb: move it to drivers/media/usb/dvb-usb Mauro Carvalho Chehab
2012-06-14 20:35 ` [PATCH RFC 06/10] [media] Rename media/dvb as media/pci Mauro Carvalho Chehab
2012-06-14 20:35 ` [PATCH RFC 07/10] [media] b2c2: break it into common/pci/usb directories Mauro Carvalho Chehab
2012-06-14 20:35 ` [PATCH RFC 08/10] [media] common: move media/common/tuners to media/tuners Mauro Carvalho Chehab
2012-06-14 20:36 ` [PATCH RFC 09/10] [media] saa7146: Move it to its own directory Mauro Carvalho Chehab
2012-06-14 20:36 ` [PATCH RFC 10/10] [media] break siano into mmc and usb directories Mauro Carvalho Chehab
2012-06-15 7:39 ` Hans Verkuil [this message]
2012-06-15 10:31 ` [PATCH RFC 00/10] media file tree reorg - part 1 Mauro Carvalho Chehab
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=4FDAE6B0.5020301@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--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 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.