All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: <torvalds@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] SG changes for 4.3
Date: Wed, 2 Sep 2015 10:58:33 -0600	[thread overview]
Message-ID: <20150902165833.GC14454@kernel.dk> (raw)

Hi Linus,

This pull request contains a set of scatter-gather related changes/fixes
for 4.3. It contains:

- Add support for limited chaining of sg tables even for architectures
  that do not set ARCH_HAS_SG_CHAIN. From Christoph.

- Add sg chain support to target_rd. From Christoph.

- Fixup open coded sg->page_link in crypto/omap-sham. From Christoph.

- Fixup open coded crypto ->page_link manipulation. From Dan.

- Also from Dan, automated fixup of manual sg_unmark_end()
  manipulations.

- Also from Dan, automated fixup of open coded sg_phys()
  implementations.

- From Robert Jarzmik, addition of an sg table splitting helper that
  drivers can use.

Please pull!


  git://git.kernel.dk/linux-block.git for-4.3/sg


----------------------------------------------------------------
Christoph Hellwig (3):
      scatterlist: allow limited chaining without ARCH_HAS_SG_CHAIN
      target/rd: always chain S/G list
      crypto/omap-sham: remove an open coded access to ->page_link

Dan Williams (3):
      crypto: replace scatterwalk_sg_chain with sg_chain
      scatterlist: remove open coded sg_unmark_end instances
      scatterlist: use sg_phys()

Robert Jarzmik (1):
      lib: scatterlist: add sg splitting function

 arch/arm/mm/dma-mapping.c                    |   2 +-
 arch/microblaze/kernel/dma.c                 |   3 +-
 block/blk-merge.c                            |   2 +-
 crypto/algif_skcipher.c                      |   2 +-
 crypto/ccm.c                                 |   8 +-
 crypto/gcm.c                                 |   4 +-
 drivers/crypto/bfin_crc.c                    |   3 +-
 drivers/crypto/omap-sham.c                   |   2 +-
 drivers/crypto/qce/sha.c                     |   2 +-
 drivers/crypto/sahara.c                      |   2 +-
 drivers/crypto/talitos.c                     |   2 +-
 drivers/iommu/intel-iommu.c                  |   4 +-
 drivers/iommu/iommu.c                        |   2 +-
 drivers/mmc/card/queue.c                     |   4 +-
 drivers/staging/android/ion/ion_chunk_heap.c |   4 +-
 drivers/target/target_core_rd.c              |  44 ------
 include/crypto/scatterwalk.h                 |  10 +-
 include/linux/scatterlist.h                  |   9 +-
 lib/Kconfig                                  |   7 +
 lib/Makefile                                 |   1 +
 lib/scatterlist.c                            |   4 -
 lib/sg_split.c                               | 202 +++++++++++++++++++++++++++
 22 files changed, 238 insertions(+), 85 deletions(-)
 create mode 100644 lib/sg_split.c

-- 
Jens Axboe


             reply	other threads:[~2015-09-02 16:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 16:58 Jens Axboe [this message]
2015-09-02 22:34 ` [GIT PULL] SG changes for 4.3 Linus Torvalds
2015-09-02 22:41   ` Jens Axboe
2015-09-02 22:50     ` Jens Axboe
2015-09-03  4:28       ` Ming Lin
2015-09-03 14:31         ` Jens Axboe

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=20150902165833.GC14454@kernel.dk \
    --to=axboe@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linuxfoundation.org \
    /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.