From: Paul Mundt <lethal@linux-sh.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>,
linux-arch@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
Dan Williams <dan.j.williams@intel.com>,
linux-sh@vger.kernel.org, Sascha Hauer <kernel@pengutronix.de>,
linux-usb@vger.kernel.org,
David Brownell <dbrownell@users.sourceforge.net>,
linux-media@vger.kernel.org,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@suse.de>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH] dma_declare_coherent_memory: push ioremap() up to caller
Date: Fri, 24 Dec 2010 00:02:10 +0000 [thread overview]
Message-ID: <20101224000210.GD28151@linux-sh.org> (raw)
In-Reply-To: <20101223235434.GA20587@n2100.arm.linux.org.uk>
On Thu, Dec 23, 2010 at 11:54:34PM +0000, Russell King - ARM Linux wrote:
> On Fri, Dec 24, 2010 at 12:20:32AM +0100, Janusz Krzysztofik wrote:
> > The patch tries to implement a solution suggested by Russell King,
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2010-December/035264.html.
> > It is expected to solve video buffer allocation issues for at least a
> > few soc_camera I/O memory less host interface drivers, designed around
> > the videobuf_dma_contig layer, which allocates video buffers using
> > dma_alloc_coherent().
> >
> > Created against linux-2.6.37-rc5.
> >
> > Tested on ARM OMAP1 based Amstrad Delta with a WIP OMAP1 camera patch,
> > patterned upon two mach-mx3 machine types which already try to use the
> > dma_declare_coherent_memory() method for reserving a region of system
> > RAM preallocated with another dma_alloc_coherent(). Compile tested for
> > all modified files except arch/sh/drivers/pci/fixups-dreamcast.c.
> >
> > Signed-off-by: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
> > ---
> > I intended to quote Russell in my commit message and even asked him for
> > his permission, but since he didn't respond, I decided to include a link
> > to his original message only.
>
> There's no problem quoting messages which were sent to public mailing
> lists, especially when there's a record of what was said in public
> archives too.
>
> I think this is definitely a step forward.
>
The -tip folks have started using LKML-Reference tags to help with this,
although I don't believe its usage is officially documented anywhere.
next prev parent reply other threads:[~2010-12-24 0:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 23:20 [PATCH] dma_declare_coherent_memory: push ioremap() up to caller Janusz Krzysztofik
2010-12-23 23:54 ` [PATCH] dma_declare_coherent_memory: push ioremap() up to Russell King - ARM Linux
2010-12-24 0:02 ` Paul Mundt [this message]
2010-12-24 1:08 ` [PATCH] dma_declare_coherent_memory: push ioremap() up to caller Janusz Krzysztofik
2010-12-24 1:58 ` Paul Mundt
2010-12-24 13:02 ` [PATCH] dma_declare_coherent_memory: push ioremap() up to Russell King - ARM Linux
2010-12-24 13:55 ` [PATCH] dma_declare_coherent_memory: push ioremap() up to caller Janusz Krzysztofik
2010-12-24 15:41 ` [PATCH] dma_declare_coherent_memory: push ioremap() up to Russell King - ARM Linux
2010-12-24 23:24 ` [PATCH] dma_declare_coherent_memory: push ioremap() up to caller Janusz Krzysztofik
2010-12-26 17:45 ` Guennadi Liakhovetski
2010-12-27 10:29 ` Janusz Krzysztofik
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=20101224000210.GD28151@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=James.Bottomley@suse.de \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dan.j.williams@intel.com \
--cc=dbrownell@users.sourceforge.net \
--cc=g.liakhovetski@gmx.de \
--cc=gregkh@suse.de \
--cc=jkrzyszt@tis.icnet.pl \
--cc=kernel@pengutronix.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).