All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>, Takashi Iwai <tiwai@suse.de>,
	Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
	alsa-devel@alsa-project.org, linux-media@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH v8] media: Add stk1160 new driver
Date: Thu, 09 Aug 2012 09:33:09 -0300	[thread overview]
Message-ID: <5023AE05.1040604@redhat.com> (raw)
In-Reply-To: <CALF0-+UqJUeCCakr73yHFjUvRVm6ZJ371wtTDKPmAXSWUB-57g@mail.gmail.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>, Takashi Iwai <tiwai@suse.de>,
	Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
	alsa-devel@alsa-project.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v8] media: Add stk1160 new driver
Date: Thu, 09 Aug 2012 09:33:09 -0300	[thread overview]
Message-ID: <5023AE05.1040604@redhat.com> (raw)
In-Reply-To: <CALF0-+UqJUeCCakr73yHFjUvRVm6ZJ371wtTDKPmAXSWUB-57g@mail.gmail.com>

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

  reply	other threads:[~2012-08-09 12:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1344260302-28849-1-git-send-email-elezegarcia@gmail.com>
2012-08-06 13:58 ` [PATCH v8] media: Add stk1160 new driver Ezequiel Garcia
2012-08-06 13:58   ` Ezequiel Garcia
2012-08-06 14:08   ` Mauro Carvalho Chehab
2012-08-06 14:08     ` Mauro Carvalho Chehab
2012-08-06 14:18     ` Hans Verkuil
2012-08-06 14:18       ` Hans Verkuil
2012-08-06 15:21       ` [alsa-devel] " Ezequiel Garcia
2012-08-06 15:42         ` Ezequiel Garcia
2012-08-06 19:13           ` Ezequiel Garcia
2012-08-06 19:13             ` Ezequiel Garcia
2012-08-09 12:24             ` [alsa-devel] " Ezequiel Garcia
2012-08-09 12:33               ` Mauro Carvalho Chehab [this message]
2012-08-09 12:33                 ` Mauro Carvalho Chehab
2012-08-09 13:57                 ` [alsa-devel] " Ezequiel Garcia
2012-08-09 20:25 ` Mauro Carvalho Chehab
2012-08-09 20:25   ` Mauro Carvalho Chehab
2012-08-09 20:43   ` Ezequiel Garcia

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=5023AE05.1040604@redhat.com \
    --to=mchehab@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=elezegarcia@gmail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=sylvester.nawrocki@gmail.com \
    --cc=tiwai@suse.de \
    /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.