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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinonWy9PqXmE3XawOcQMDjM94K18z4NCUqac=e7@mail.gmail.com>
Date:	Thu, 20 Jan 2011 15:09:35 +0530
From:	halli manjunatha <manjunatha_halli@...com>
To:	linux-media@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC V10 3/7] drivers:media:radio: wl128x: FM Driver Common sources

Hi Mauro,

We don't maintain a separate tree for these v4l2 drivers. We generally
use the linux-omap tree for our day to day activities, However the
drivers posted here has also been tested on the linux-2.6.37-rc7,
So it is directly applicable on the k.org tree.

So, I was hoping you can merge these patches on the v4l2 tree on the
kernel.org and thereby it gets pulled into the mainline, when linus
would pull your tree.

It would also help for us for it to be on v4l2 tree, since it would
mean you and Hans have also reviewed it :).

Regards
Manjunatha Halli



On Thu, Jan 20, 2011 at 12:42 AM, Mauro Carvalho Chehab
<mchehab@...radead.org> wrote:
> Manju,
>
> Em 18-01-2011 11:19, halli manjunatha escreveu:
>>  have a look at the driver it’s already reviewed by Hans Verkuil.
>> Please let me know if you are okay to include this in mainline.
>
> As I've already pointed you, just send me a pull request from your tree when
> you think it is ready. I'll be reviewing it after that. There are just too much
> reviews on those drivers from TI for me to dig into every single version, especially
> since, on most cases, I can't really contribute much, as I don't have OMAP3/Davinci
> datasheets and the required devices here for testing, and that the reviews
> come from someone at TI and/or one of your customers with a real test case
> scenario.
>
> So, as agreed in the past, I just mark all those drivers with RFC at patchwork
> and I wait for the driver maintainer to send me a pull request, indicating me
> that you've reached on a point where the driver/patch series is ready for its
> addition.
>
> So, if you think you're ready, you just need to send a pull request to the ML.
> You don't even need to c/c me on that (and please avoid doing it, otherwise
> I end by having multiple copies of your pull request, flooding my email with no
> good reason).
>
> Thanks,
> Mauro
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Regards
Halli
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ