Re: [alsa-devel] [PATCH v8] media: Add stk1160 new driver
Hi Mauro,
On Mon, Aug 6, 2012 at 10:38 AM, Ezequiel Garcia elezegarcia@gmail.com wrote:
This driver adds support for stk1160 usb bridge as used in some video/audio usb capture devices. It is a complete rewrite of staging/media/easycap driver and it's expected as a replacement.
I just sent v8, but it looks it wasn't received by patchwork either.
What's going on?
Regards, Ezequiel.
Em 06-08-2012 10:58, Ezequiel Garcia escreveu:
Hi Mauro,
On Mon, Aug 6, 2012 at 10:38 AM, Ezequiel Garcia elezegarcia@gmail.com wrote:
This driver adds support for stk1160 usb bridge as used in some video/audio usb capture devices. It is a complete rewrite of staging/media/easycap driver and it's expected as a replacement.
I just sent v8, but it looks it wasn't received by patchwork either.
What's going on?
The patch didn't arrive at linux-media ML.
Not sure why it got rejected at vger. I suggest you to ping vger admin to see why your patches are being rejected there.
I tested parsing this patch manually and patchwork accepted. So, once the issue with vger is solved, other patches should be properly handled there.
Regards, Mauro
On Mon August 6 2012 16:08:33 Mauro Carvalho Chehab wrote:
Em 06-08-2012 10:58, Ezequiel Garcia escreveu:
Hi Mauro,
On Mon, Aug 6, 2012 at 10:38 AM, Ezequiel Garcia elezegarcia@gmail.com wrote:
This driver adds support for stk1160 usb bridge as used in some video/audio usb capture devices. It is a complete rewrite of staging/media/easycap driver and it's expected as a replacement.
I just sent v8, but it looks it wasn't received by patchwork either.
What's going on?
The patch didn't arrive at linux-media ML.
Not sure why it got rejected at vger. I suggest you to ping vger admin to see why your patches are being rejected there.
I tested parsing this patch manually and patchwork accepted. So, once the issue with vger is solved, other patches should be properly handled there.
Could it be related to the fact that a gmail account is used? Konke Radlow had a similar issue recently when he posted a patch from a gmail account. It worked fine when posted from a company account.
Regards,
Hans
On Mon, Aug 6, 2012 at 11:18 AM, Hans Verkuil hverkuil@xs4all.nl wrote:
On Mon August 6 2012 16:08:33 Mauro Carvalho Chehab wrote:
Em 06-08-2012 10:58, Ezequiel Garcia escreveu:
Hi Mauro,
On Mon, Aug 6, 2012 at 10:38 AM, Ezequiel Garcia elezegarcia@gmail.com wrote:
This driver adds support for stk1160 usb bridge as used in some video/audio usb capture devices. It is a complete rewrite of staging/media/easycap driver and it's expected as a replacement.
I just sent v8, but it looks it wasn't received by patchwork either.
What's going on?
The patch didn't arrive at linux-media ML.
Not sure why it got rejected at vger. I suggest you to ping vger admin to see why your patches are being rejected there.
I tested parsing this patch manually and patchwork accepted. So, once the issue with vger is solved, other patches should be properly handled there.
Could it be related to the fact that a gmail account is used? Konke Radlow had a similar issue recently when he posted a patch from a gmail account. It worked fine when posted from a company account.
FWIW, I've always sent my patches from git-send-email through my gmail account. Don't know if this is an issue, but it never seemed to.
Regards, Ezequiel.
Hi Mauro,
On Mon, Aug 6, 2012 at 12:21 PM, Ezequiel Garcia elezegarcia@gmail.com wrote:
On Mon, Aug 6, 2012 at 11:18 AM, Hans Verkuil hverkuil@xs4all.nl wrote:
On Mon August 6 2012 16:08:33 Mauro Carvalho Chehab wrote:
Em 06-08-2012 10:58, Ezequiel Garcia escreveu:
Hi Mauro,
On Mon, Aug 6, 2012 at 10:38 AM, Ezequiel Garcia elezegarcia@gmail.com wrote:
This driver adds support for stk1160 usb bridge as used in some video/audio usb capture devices. It is a complete rewrite of staging/media/easycap driver and it's expected as a replacement.
I just sent v8, but it looks it wasn't received by patchwork either.
What's going on?
The patch didn't arrive at linux-media ML.
Not sure why it got rejected at vger. I suggest you to ping vger admin to see why your patches are being rejected there.
I tested parsing this patch manually and patchwork accepted. So, once the issue with vger is solved, other patches should be properly handled there.
Could it be related to the fact that a gmail account is used? Konke Radlow had a similar issue recently when he posted a patch from a gmail account. It worked fine when posted from a company account.
FWIW, I've always sent my patches from git-send-email through my gmail account. Don't know if this is an issue, but it never seemed to.
On a second thought, perhaps it makes sense to have a git repo (on linuxtv.org) for me to work on stk1160. That way I could simply send "git pull" requests instead of patches.
I'm not sure if this is a better workflow and/or would allow for easier reviewing.
Thanks, Ezequiel.
Hello,
On Mon, Aug 6, 2012 at 12:42 PM, Ezequiel Garcia elezegarcia@gmail.com wrote:
Hi Mauro,
On Mon, Aug 6, 2012 at 12:21 PM, Ezequiel Garcia elezegarcia@gmail.com wrote:
On Mon, Aug 6, 2012 at 11:18 AM, Hans Verkuil hverkuil@xs4all.nl wrote:
On Mon August 6 2012 16:08:33 Mauro Carvalho Chehab wrote:
Em 06-08-2012 10:58, Ezequiel Garcia escreveu:
Hi Mauro,
On Mon, Aug 6, 2012 at 10:38 AM, Ezequiel Garcia elezegarcia@gmail.com wrote:
This driver adds support for stk1160 usb bridge as used in some video/audio usb capture devices. It is a complete rewrite of staging/media/easycap driver and it's expected as a replacement.
I just sent v8, but it looks it wasn't received by patchwork either.
What's going on?
The patch didn't arrive at linux-media ML.
Not sure why it got rejected at vger. I suggest you to ping vger admin to see why your patches are being rejected there.
I tested parsing this patch manually and patchwork accepted. So, once the issue with vger is solved, other patches should be properly handled there.
Could it be related to the fact that a gmail account is used? Konke Radlow had a similar issue recently when he posted a patch from a gmail account. It worked fine when posted from a company account.
FWIW, I've always sent my patches from git-send-email through my gmail account. Don't know if this is an issue, but it never seemed to.
On a second thought, perhaps it makes sense to have a git repo (on linuxtv.org) for me to work on stk1160. That way I could simply send "git pull" requests instead of patches.
I'm not sure if this is a better workflow and/or would allow for easier reviewing.
Well, I just got an answer from vger administrator. He told me the patch was exceeding the allowed limit. Which I later discovered it was documented here:
http://vger.kernel.org/majordomo-info.html
Apparently, there is a 100, 000 characters limit.
So, how do we proceed?
Regards, Ezequiel.
Hi Mauro,
On Mon, Aug 6, 2012 at 4:13 PM, Ezequiel Garcia elezegarcia@gmail.com wrote:
On a second thought, perhaps it makes sense to have a git repo (on linuxtv.org) for me to work on stk1160. That way I could simply send "git pull" requests instead of patches.
I'm not sure if this is a better workflow and/or would allow for easier reviewing.
Well, I just got an answer from vger administrator. He told me the patch was exceeding the allowed limit. Which I later discovered it was documented here:
http://vger.kernel.org/majordomo-info.html
Apparently, there is a 100, 000 characters limit.
So, how do we proceed?
Ping! Could you take a look at this? I'd like to solve the pending issues (see previous mails), in order to know if the driver will need further work.
... or perhaps we can leave this for after the merge window, when you (and everyone) are be less busy.
I *really* hope I'm not spamming. In that case, feel free to say so. Thanks, Ezequiel.
Em 09-08-2012 09:24, Ezequiel Garcia escreveu:
Hi Mauro,
On Mon, Aug 6, 2012 at 4:13 PM, Ezequiel Garcia elezegarcia@gmail.com wrote:
On a second thought, perhaps it makes sense to have a git repo (on linuxtv.org) for me to work on stk1160. That way I could simply send "git pull" requests instead of patches.
I'm not sure if this is a better workflow and/or would allow for easier reviewing.
Well, I just got an answer from vger administrator. He told me the patch was exceeding the allowed limit. Which I later discovered it was documented here:
http://vger.kernel.org/majordomo-info.html
Apparently, there is a 100, 000 characters limit.
So, how do we proceed?
Ping! Could you take a look at this? I'd like to solve the pending issues (see previous mails), in order to know if the driver will need further work.
... or perhaps we can leave this for after the merge window, when you (and everyone) are be less busy.
I *really* hope I'm not spamming. In that case, feel free to say so.
The merge window was closed already. I pushed this patch directly into patchwork, so I should be handling it sooner or later.
Unfortunately, I had a crash on my home volume group, and I'm busy those days recovering data from it. It seems I'll be able to recover everything, but I'll need to move about 800GB of data between two disks (one of them is a slow one), plus my backup machine. I'll likely break it into several smaller logical volumes, in order to help me to keep the backup updated. So, that'll keep me busy for a while. In the meantime, I'm working on a slow notebook. So, I might still be able to review and add some patches upstream, especially the more trivial ones.
Regards, Mauro
On Thu, Aug 9, 2012 at 9:33 AM, Mauro Carvalho Chehab mchehab@redhat.com wrote:
Em 09-08-2012 09:24, Ezequiel Garcia escreveu:
Hi Mauro,
On Mon, Aug 6, 2012 at 4:13 PM, Ezequiel Garcia elezegarcia@gmail.com wrote:
On a second thought, perhaps it makes sense to have a git repo (on linuxtv.org) for me to work on stk1160. That way I could simply send "git pull" requests instead of patches.
I'm not sure if this is a better workflow and/or would allow for easier reviewing.
Well, I just got an answer from vger administrator. He told me the patch was exceeding the allowed limit. Which I later discovered it was documented here:
http://vger.kernel.org/majordomo-info.html
Apparently, there is a 100, 000 characters limit.
So, how do we proceed?
Ping! Could you take a look at this? I'd like to solve the pending issues (see previous mails), in order to know if the driver will need further work.
... or perhaps we can leave this for after the merge window, when you (and everyone) are be less busy.
I *really* hope I'm not spamming. In that case, feel free to say so.
The merge window was closed already.
Yes, you're right. I'm still unsure about the work flow.
I pushed this patch directly into patchwork, so I should be handling it sooner or later.
Yes, I noticed it after sending the mail.
Unfortunately, I had a crash on my home volume group, and I'm busy those days recovering data from it. It seems I'll be able to recover everything, but I'll need to move about 800GB of data between two disks (one of them is a slow one), plus my backup machine. I'll likely break it into several smaller logical volumes, in order to help me to keep the backup updated. So, that'll keep me busy for a while. In the meantime, I'm working on a slow notebook. So, I might still be able to review and add some patches upstream, especially the more trivial ones.
Ouch! I'm sorry to hear that. I hope you can recover soon.
I'll stay tuned for your comments (and I'll stop bothering).
Thanks for your reply! Ezequiel.
participants (3)
-
Ezequiel Garcia -
Hans Verkuil -
Mauro Carvalho Chehab