Prev: [NEXT] add x86 platform driver tree
Next: Fwd: A weird multi-thread performance problem
From: Spyros Papageorgiou on 31 May 2010 11:10
From:Spyros Papageorgiou <spyros.papageorgiou(a)gmai.com>

Removed an unneeded struct specifier in function call.

Signed-off-by: Spyros Papageorgiou <spyros.papageorgiou(a)gmai.com>
---
drivers/staging/memrar/memrar_allocator.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/staging/memrar/memrar_allocator.c b/drivers/staging/memrar/memrar_allocator.c
index a4f8c58..db37c6a 100644
--- a/drivers/staging/memrar/memrar_allocator.c
+++ b/drivers/staging/memrar/memrar_allocator.c
@@ -276,7 +276,7 @@ long memrar_allocator_free(struct memrar_allocator *allocator,

struct memrar_address_range * const chunk =
&list_entry(pos,
- struct memrar_address_ranges,
+ memrar_address_ranges,
list)->range;

/* Extend size of existing free adjacent chunk. */
@@ -300,7 +300,7 @@ long memrar_allocator_free(struct memrar_allocator *allocator,

struct memrar_address_ranges const * const next =
list_entry(pos->next,
- struct memrar_address_ranges,
+ memrar_address_ranges,
list);

chunk->end = handle->end;
@@ -352,7 +352,7 @@ long memrar_allocator_free(struct memrar_allocator *allocator,

struct memrar_address_ranges const * const prev =
list_entry(pos->prev,
- struct memrar_address_ranges,
+ memrar_address_ranges,
list);

chunk->begin = handle->begin;
--
1.7.0.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [NEXT] add x86 platform driver tree
Next: Fwd: A weird multi-thread performance problem