From: Nick Holloway <Nick.Holloway@pyrites.org.uk>
To: Nick Piggin <npiggin@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/5] mm: improve remapping of vmalloc regions
Date: Tue, 2 May 2006 17:30:31 +0100 [thread overview]
Message-ID: <20060502163031.GA32629@pyrites.org.uk> (raw)
In-Reply-To: <20060228202202.14172.60409.sendpatchset@linux.site>
On Thu, Apr 20, 2006 at 05:06:09PM +0000, Nick Piggin wrote:
> Not tested, because I don't have any of the hardware, but it seems
> compiles OK.
I have a CPIA webcam, so I have taken 2.6.17-rc3 and added your patchset
on top.
The patch is working fine, using "motion" as the video4linux application
accessing the parallel port CPIA webcam.
--
`O O' | Nick.Holloway@pyrites.org.uk
// ^ \\ | http://www.pyrites.org.uk/
next prev parent reply other threads:[~2006-05-02 16:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 17:06 [patch 0/5] mm: improve remapping of vmalloc regions Nick Piggin
2006-04-20 17:06 ` [patch 1/5] mm: remap_vmalloc_range Nick Piggin
2006-04-20 17:22 ` Christoph Hellwig
2006-04-20 17:33 ` Nick Piggin
2006-04-20 18:09 ` Nick Piggin
2006-04-20 17:06 ` [patch 2/5] mm: deprecate vmalloc_to_pfn Nick Piggin
2006-04-20 17:22 ` Christoph Hellwig
2006-04-20 17:36 ` Nick Piggin
2006-04-20 20:03 ` Andrew Morton
2006-04-20 17:06 ` [patch 3/5] mm: remove rvmalloc Nick Piggin
2006-04-20 17:06 ` [patch 4/5] mm: extra remap_vmalloc_range check Nick Piggin
2006-04-20 17:07 ` [patch 5/5] drivers: leave vm_flags alone Nick Piggin
2006-04-20 17:27 ` [patch 6/5] mm: find_vm_area locking fixes Nick Piggin
2006-04-20 18:14 ` [patch][rfc] improve remap_vmalloc_range callers' return values Nick Piggin
2006-05-02 16:30 ` Nick Holloway [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-21 6:43 [patch 0/5] mm: improve remapping of vmalloc regions Nick Piggin
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=20060502163031.GA32629@pyrites.org.uk \
--to=nick.holloway@pyrites.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox