| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <AANLkTinyaZ07HBFNHNyR9eK6__QdZtG6O1gQX1F+YRB9@mail.gmail.com> Date: Thu, 18 Nov 2010 11:24:16 +0530 From: Pavan Savoy <pavan_savoy@...com> To: Ohad Ben-Cohen <ohad@...ery.com>, mchehab@...radead.org, hverkuil@...all.nl Cc: manjunatha_halli@...com, linux-kernel@...r.kernel.org, linux-media@...r.kernel.org Subject: Re: [PATCH v4 0/6] FM V4L2 drivers for WL128x Hans, Mauro, Ohad, On Wed, Nov 17, 2010 at 6:32 PM, Ohad Ben-Cohen <ohad@...ery.com> wrote: > Hi Manjunatha, > > On Tue, Nov 16, 2010 at 3:18 PM, <manjunatha_halli@...com> wrote: >> drivers/staging/ti-st/Kconfig | 10 + >> drivers/staging/ti-st/Makefile | 2 + >> drivers/staging/ti-st/fmdrv.h | 259 ++++ >> drivers/staging/ti-st/fmdrv_common.c | 2141 ++++++++++++++++++++++++++++++++++ >> drivers/staging/ti-st/fmdrv_common.h | 458 ++++++++ >> drivers/staging/ti-st/fmdrv_rx.c | 979 ++++++++++++++++ >> drivers/staging/ti-st/fmdrv_rx.h | 59 + >> drivers/staging/ti-st/fmdrv_tx.c | 461 ++++++++ >> drivers/staging/ti-st/fmdrv_tx.h | 37 + >> drivers/staging/ti-st/fmdrv_v4l2.c | 757 ++++++++++++ >> drivers/staging/ti-st/fmdrv_v4l2.h | 32 + >> 11 files changed, 5195 insertions(+), 0 deletions(-) > > Usually when a driver is added to staging, it should also have a TODO > file specifying what needs to be done before the driver can be taken > out of staging (at least as far as the author knows of today). > > It helps keeping track of the open issues in the driver, which is good > for everyone - the author, the random contributor/observer, and > probably even the staging maintainer. > > Can you please add such a TODO file ? > > Thanks, > Ohad. Thanks Ohad, for the comments, We do have an internal TODO. In terms of functionality we have stuff like TX RDS which already has few CIDs in the extended controls. extend V4L2 for complete-scan, add in stop search during hw_seek .. etc... But I just wanted to ask whether this is good enough to be staged. Because as we begin to implement and add in the items in TODO - the patch set will keep continuing to grow. So Hans, Mauro, What do you think ? It would be real helpful - if this can be staged, it is becoming difficult to maintain for us. Thanks, Pavan >> create mode 100644 drivers/staging/ti-st/fmdrv.h >> create mode 100644 drivers/staging/ti-st/fmdrv_common.c >> create mode 100644 drivers/staging/ti-st/fmdrv_common.h >> create mode 100644 drivers/staging/ti-st/fmdrv_rx.c >> create mode 100644 drivers/staging/ti-st/fmdrv_rx.h >> create mode 100644 drivers/staging/ti-st/fmdrv_tx.c >> create mode 100644 drivers/staging/ti-st/fmdrv_tx.h >> create mode 100644 drivers/staging/ti-st/fmdrv_v4l2.c >> create mode 100644 drivers/staging/ti-st/fmdrv_v4l2.h >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >> the body of a message to majordomo@...r.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> Please read the FAQ at http://www.tux.org/lkml/ >> > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists