From: Mitchel Humpherys <mitchelh@codeaurora.org>
To: Heesub Shin <heesub.shin@samsung.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"John Stultz" <john.stultz@linaro.org>,
"Rebecca Schultz Zavin" <rebecca@android.com>,
"Colin Cross" <ccross@android.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Daeseok Youn" <daeseok.youn@gmail.com>,
"Sunghwan Yun" <sunghwan.yun@samsung.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/9] staging: ion: remove struct page_info
Date: Tue, 27 May 2014 11:36:07 -0700 [thread overview]
Message-ID: <vnkw61kr5aso.fsf@mitchelh-linux.qualcomm.com> (raw)
In-Reply-To: <1401098701-24049-6-git-send-email-heesub.shin@samsung.com> (Heesub Shin's message of "Mon, 26 May 2014 19:04:58 +0900")
On Mon, May 26 2014 at 03:04:58 AM, Heesub Shin <heesub.shin@samsung.com> wrote:
> ION system heap uses a temporary list holding meta data on pages
> allocated to build scatter/gather table. Now that the pages are compound
> pages, we do not need to introduce a new data type redundantly.
>
> Signed-off-by: Heesub Shin <heesub.shin@samsung.com>
> ---
> drivers/staging/android/ion/ion_system_heap.c | 47 +++++++++------------------
> 1 file changed, 15 insertions(+), 32 deletions(-)
>
> diff --git a/drivers/staging/android/ion/ion_system_heap.c b/drivers/staging/android/ion/ion_system_heap.c
> index 73a2e67..f0ae210 100644
> --- a/drivers/staging/android/ion/ion_system_heap.c
> +++ b/drivers/staging/android/ion/ion_system_heap.c
> @@ -51,11 +51,6 @@ struct ion_system_heap {
> struct ion_page_pool **pools;
> };
>
> -struct page_info {
> - struct page *page;
> - struct list_head list;
> -};
> -
> static struct page *alloc_buffer_page(struct ion_system_heap *heap,
> struct ion_buffer *buffer,
> unsigned long order)
> @@ -96,19 +91,14 @@ static void free_buffer_page(struct ion_system_heap *heap,
> }
>
>
> -static struct page_info *alloc_largest_available(struct ion_system_heap *heap,
> - struct ion_buffer *buffer,
> - unsigned long size,
> - unsigned int max_order)
> +static struct page *alloc_largest_available(struct ion_system_heap *heap,
> + struct ion_buffer *buffer,
> + unsigned long size,
> + unsigned int max_order)
Was this whitespace-only change intentional?
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-05-27 18:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 10:04 [PATCH 1/9] staging: ion: tidy up a bit Heesub Shin
2014-05-26 10:04 ` [PATCH 2/9] staging: ion: simplify ion_page_pool_total() Heesub Shin
2014-05-26 10:04 ` [PATCH 3/9] staging: ion: use compound pages on high order pages for system heap Heesub Shin
2014-05-26 10:04 ` [PATCH 4/9] staging: ion: remove struct ion_page_pool_item Heesub Shin
2014-05-27 0:39 ` Heesub Shin
2014-05-26 10:04 ` [PATCH 5/9] staging: ion: remove order from struct page_info Heesub Shin
2014-05-26 10:04 ` [PATCH 6/9] staging: ion: remove " Heesub Shin
2014-05-27 18:36 ` Mitchel Humpherys [this message]
2014-05-27 21:16 ` Dan Carpenter
2014-05-26 10:04 ` [PATCH 7/9] staging: ion: remove order argument from free_buffer_page() Heesub Shin
2014-05-27 18:37 ` Mitchel Humpherys
2014-05-26 10:05 ` [PATCH 8/9] staging: ion: shrink highmem pages on kswapd Heesub Shin
2014-05-26 10:05 ` [PATCH 9/9] staging: ion: optimize struct ion_system_heap Heesub Shin
2014-05-26 10:36 ` [PATCH 1/9] staging: ion: tidy up a bit Dan Carpenter
2014-05-27 0:58 ` Heesub Shin
2014-05-27 9:55 ` Dan Carpenter
2014-05-27 18:52 ` Greg Kroah-Hartman
2014-05-27 18:59 ` John Stultz
2014-05-28 6:52 ` [PATCH v2 0/9] staging: ion: system heap and page pool fixes Heesub Shin
2014-05-28 6:52 ` [PATCH v2 1/9] staging: ion: tidy up a bit Heesub Shin
2014-05-29 20:42 ` Greg Kroah-Hartman
2014-05-30 1:22 ` Heesub Shin
2014-05-30 1:26 ` [PATCH v2 RESEND 1/4] staging: ion: remove order from struct page_info Heesub Shin
2014-05-30 1:26 ` [PATCH v2 RESEND 2/4] staging: ion: remove " Heesub Shin
2014-05-30 1:26 ` [PATCH v2 RESEND 3/4] staging: ion: remove order argument from free_buffer_page() Heesub Shin
2014-05-30 1:26 ` [PATCH v2 RESEND 4/4] staging: ion: optimize struct ion_system_heap Heesub Shin
2014-05-28 6:52 ` [PATCH v2 2/9] staging: ion: simplify ion_page_pool_total() Heesub Shin
2014-05-28 6:52 ` [PATCH v2 3/9] staging: ion: remove struct ion_page_pool_item Heesub Shin
2014-05-28 6:52 ` [PATCH v2 4/9] staging: ion: use compound pages on high order pages for system heap Heesub Shin
2014-05-28 6:52 ` [PATCH v2 5/9] staging: ion: remove order from struct page_info Heesub Shin
2014-05-28 6:52 ` [PATCH v2 6/9] staging: ion: remove " Heesub Shin
2014-05-28 6:52 ` [PATCH v2 7/9] staging: ion: remove order argument from free_buffer_page() Heesub Shin
2014-05-28 6:52 ` [PATCH v2 8/9] staging: ion: shrink highmem pages on kswapd Heesub Shin
2014-05-28 6:53 ` [PATCH v2 9/9] staging: ion: optimize struct ion_system_heap Heesub Shin
2014-05-28 16:28 ` [PATCH v2 0/9] staging: ion: system heap and page pool fixes Mitchel Humpherys
2014-05-28 20:01 ` John Stultz
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=vnkw61kr5aso.fsf@mitchelh-linux.qualcomm.com \
--to=mitchelh@codeaurora.org \
--cc=arve@android.com \
--cc=ccross@android.com \
--cc=daeseok.youn@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=heesub.shin@samsung.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rebecca@android.com \
--cc=sunghwan.yun@samsung.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