From: Jens Axboe <jens.axboe@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: Jens Axboe <jens.axboe@oracle.com>
Subject: [PATCH 1/19] crypto: don't pollute the global namespace with sg_next()
Date: Wed, 16 May 2007 10:32:15 +0200 [thread overview]
Message-ID: <11793043532702-git-send-email-jens.axboe@oracle.com> (raw)
In-Reply-To: <11793043533744-git-send-email-jens.axboe@oracle.com>
It's a subsystem function, prefix it as such.
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
---
crypto/digest.c | 2 +-
crypto/scatterwalk.c | 2 +-
crypto/scatterwalk.h | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/crypto/digest.c b/crypto/digest.c
index 1bf7414..e56de67 100644
--- a/crypto/digest.c
+++ b/crypto/digest.c
@@ -77,7 +77,7 @@ static int update2(struct hash_desc *desc,
if (!nbytes)
break;
- sg = sg_next(sg);
+ sg = scatterwalk_sg_next(sg);
}
return 0;
diff --git a/crypto/scatterwalk.c b/crypto/scatterwalk.c
index 81afd17..2e51f82 100644
--- a/crypto/scatterwalk.c
+++ b/crypto/scatterwalk.c
@@ -70,7 +70,7 @@ static void scatterwalk_pagedone(struct scatter_walk *walk, int out,
walk->offset += PAGE_SIZE - 1;
walk->offset &= PAGE_MASK;
if (walk->offset >= walk->sg->offset + walk->sg->length)
- scatterwalk_start(walk, sg_next(walk->sg));
+ scatterwalk_start(walk, scatterwalk_sg_next(walk->sg));
}
}
diff --git a/crypto/scatterwalk.h b/crypto/scatterwalk.h
index f1592cc..e049c62 100644
--- a/crypto/scatterwalk.h
+++ b/crypto/scatterwalk.h
@@ -20,7 +20,7 @@
#include "internal.h"
-static inline struct scatterlist *sg_next(struct scatterlist *sg)
+static inline struct scatterlist *scatterwalk_sg_next(struct scatterlist *sg)
{
return (++sg)->length ? sg : (void *)sg->page;
}
--
1.5.2.rc1
next prev parent reply other threads:[~2007-05-16 8:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 8:32 [PATCH 0/19] Chaining sg lists for big IO commands v6 Jens Axboe
2007-05-16 8:32 ` Jens Axboe [this message]
2007-05-16 8:32 ` [PATCH 2/19] Add sg helpers for iterating over a scatterlist table Jens Axboe
2007-05-16 8:32 ` [PATCH 3/19] libata: convert to using sg helpers Jens Axboe
2007-05-16 8:32 ` [PATCH 4/19] block: " Jens Axboe
2007-05-16 8:32 ` [PATCH 5/19] scsi: " Jens Axboe
2007-05-16 11:17 ` Cornelia Huck
2007-05-16 11:25 ` Jens Axboe
2007-05-16 8:32 ` [PATCH 6/19] Add chained sg support to linux/scatterlist.h Jens Axboe
2007-05-16 8:32 ` [PATCH 7/19] i386 dma_map_sg: convert to using sg helpers Jens Axboe
2007-05-16 8:32 ` [PATCH 8/19] i386: enable sg chaining Jens Axboe
2007-05-16 8:32 ` [PATCH 9/19] swiotlb: sg chaining support Jens Axboe
2007-05-16 8:32 ` [PATCH 10/19] x86-64: update iommu/dma mapping functions to sg helpers Jens Axboe
2007-05-16 8:32 ` [PATCH 11/19] x86-64: enable sg chaining Jens Axboe
2007-05-16 8:32 ` [PATCH 12/19] IA64: sg chaining support Jens Axboe
2007-05-16 8:32 ` [PATCH 13/19] PPC: " Jens Axboe
2007-05-16 8:32 ` [PATCH 14/19] SPARC: " Jens Axboe
2007-05-16 8:32 ` [PATCH 15/19] SPARC64: " Jens Axboe
2007-05-16 8:32 ` [PATCH 16/19] scsi: simplify scsi_free_sgtable() Jens Axboe
2007-05-16 8:32 ` [PATCH 17/19] SCSI: support for allocating large scatterlists Jens Axboe
2007-05-16 8:32 ` [PATCH 18/19] ll_rw_blk: temporarily enable max_segments tweaking Jens Axboe
2007-05-16 8:32 ` [PATCH 19/19] drivers: sg chaining support 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=11793043532702-git-send-email-jens.axboe@oracle.com \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome