From: Mark Brown <broonie@kernel.org>
To: Franklin S Cooper Jr <fcooper@ti.com>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
david.s.gordon@intel.com, akpm@linux-foundation.org,
nsekhar@ti.com, vigneshr@ti.com, peter.ujfalusi@ti.com
Subject: Re: [RFC] [PATCH 1/3] lib/scatterlist: Add support to clone sg_table
Date: Wed, 22 Jun 2016 16:18:03 +0100 [thread overview]
Message-ID: <20160622151803.GP28202@sirena.org.uk> (raw)
In-Reply-To: <1466203513-4771-2-git-send-email-fcooper@ti.com>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
On Fri, Jun 17, 2016 at 05:45:11PM -0500, Franklin S Cooper Jr wrote:
> Occasionally there are times you need to tweak a S/G table while
> maintaining the original table. This function will duplicate the passed
> in S/G table along with its chained sgl and return a pointer to the cloned
> copy.
You ought to send this to whoever looks after the scatterlist code as
well, or at least a wider circulation. Unfortunately that doesn't look
100% clear... off the top of my head Jens Axboe and Andrew Morton look
like good candidates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-22 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 22:45 [RFC] [PATCH 0/3] scatterlist: Add support to clone sg_table Franklin S Cooper Jr
2016-06-17 22:45 ` [RFC] [PATCH 1/3] lib/scatterlist: " Franklin S Cooper Jr
2016-06-22 15:18 ` Mark Brown [this message]
2016-06-17 22:45 ` [RFC] [PATCH 2/3] spi: omap2-mcspi: Add comments for RX only DMA buffer workaround Franklin S Cooper Jr
2016-07-05 14:50 ` Applied "spi: omap2-mcspi: Add comments for RX only DMA buffer workaround" to the spi tree Mark Brown
2016-06-17 22:45 ` [RFC] [PATCH 3/3] spi: omap2-mcspi: Use the SPI framework to handle DMA mapping Franklin S Cooper Jr
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=20160622151803.GP28202@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david.s.gordon@intel.com \
--cc=fcooper@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=vigneshr@ti.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