From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Florian Mickler <florian@mickler.org>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
crope@iki.fi, tvboxspy@gmail.com
Subject: Re: [PATCH 0/5] get rid of on-stack dma buffers (part1)
Date: Sat, 30 Apr 2011 19:30:52 -0300 [thread overview]
Message-ID: <4DBC8D9C.2090802@redhat.com> (raw)
In-Reply-To: <20110430205405.4beb7d33@schatten.dmk.lab>
Hi Florian,
Em 30-04-2011 15:54, Florian Mickler escreveu:
> Hi Mauro!
>
> I just saw that you picked up some patches of mine. What about these?
> These are actually tested...
I'm still in process of applying the pending patches. Due to patchwork.kernel.org
troubles (including the loss of about 270 patches from its SQL database only
recovered yesterday[1]), I have a long backlog. So, I'm gradually applying the remaing
stuff. It will take some time though, and it will depend on patchwork mood, but I intend
to spend some time during this weekend to minimize the backlog.
Cheers,
Mauro
[1] The recover lost the email's body/SOB, so I've wrote a script to use my email
queue to get the data, using patchwork just to mark what patches were already
processed. This increses the time I have to spend on each patch, as I need to run
a script to match the patchwork patch with the patch ID inside my email queue.
>
> Regards,
> Flo
>
> On Sun, 20 Mar 2011 22:50:47 +0100
> Florian Mickler <florian@mickler.org> wrote:
>
>> Hi Mauro!
>>
>> These are the patches which got tested already and
>> should be good to go. [first batch of patches]
>>
>> I have another batch with updated patches (dib0700, gp8psk, vp702x)
>> where I did some more extensive changes to use preallocated memory.
>> And a small update to the vp7045 patch.
>>
>> Third batch are the patches to opera1, m920x, dw2102, friio,
>> a800 which I left as is, for the time beeing.
>> Regards,
>> Flo
>>
>> Florian Mickler (5):
>> [media] ec168: get rid of on-stack dma buffers
>> [media] ce6230: get rid of on-stack dma buffer
>> [media] au6610: get rid of on-stack dma buffer
>> [media] lmedm04: correct indentation
>> [media] lmedm04: get rid of on-stack dma buffers
>>
>> drivers/media/dvb/dvb-usb/au6610.c | 22 ++++++++++++++++------
>> drivers/media/dvb/dvb-usb/ce6230.c | 11 +++++++++--
>> drivers/media/dvb/dvb-usb/ec168.c | 18 +++++++++++++++---
>> drivers/media/dvb/dvb-usb/lmedm04.c | 35 +++++++++++++++++++++++------------
>> 4 files changed, 63 insertions(+), 23 deletions(-)
>>
next prev parent reply other threads:[~2011-04-30 22:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 21:50 [PATCH 0/5] get rid of on-stack dma buffers (part1) Florian Mickler
2011-03-20 21:50 ` [PATCH 1/5] [media] ec168: get rid of on-stack dma buffers Florian Mickler
2011-03-20 21:50 ` [PATCH 2/5] [media] ce6230: get rid of on-stack dma buffer Florian Mickler
2011-03-20 21:50 ` [PATCH 3/5] [media] au6610: " Florian Mickler
2011-03-20 21:50 ` [PATCH 4/5] [media] lmedm04: correct indentation Florian Mickler
2011-03-20 21:50 ` [PATCH 5/5 v2] [media] lmedm04: get rid of on-stack dma buffers Florian Mickler
2011-04-30 18:54 ` [PATCH 0/5] get rid of on-stack dma buffers (part1) Florian Mickler
2011-04-30 22:30 ` Mauro Carvalho Chehab [this message]
2011-05-01 10:38 ` Florian Mickler
2011-05-01 15:59 ` 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=4DBC8D9C.2090802@redhat.com \
--to=mchehab@redhat.com \
--cc=crope@iki.fi \
--cc=florian@mickler.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=tvboxspy@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).