From: Umang Jain <umang.jain@ideasonboard.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Stefan Wahren <wahrenst@gmx.net>
Subject: Re: [PATCH 0/3] staging: vchiq_core: Consolidate bulk xfer helper
Date: Thu, 26 Sep 2024 09:40:37 +0530 [thread overview]
Message-ID: <b7e0d579-a3c5-42ee-a65c-945f5c368124@ideasonboard.com> (raw)
In-Reply-To: <6661b2d5-b439-46e1-b240-9fe436db4e67@stanley.mountain>
Hi Dan,
On 25/09/24 2:53 pm, Dan Carpenter wrote:
> On Thu, Sep 19, 2024 at 07:51:27PM +0530, Umang Jain wrote:
>> Few functions were identified were their declaration, definition
>> and usage were spread (incorrectly) across vchiq_core and vchiq_arm.
>>
>> These are being consolidated into vchiq_core in this series.
>> Please look at individual patches for details.
>>
>> 2/3 is in particular a big one. The code is just a move, but
>> seems big - as it was diffcult to split it into smaller, compilable
>> hunks of individual patches.
>>
>> Umang Jain (3):
>> staging: vchiq_core: Move remote_event_signal() vchiq_core
>> staging: vchiq_core: Move bulk data functions in vchiq_core
>> staging: vchiq_core: Drop vchiq_pagelist.h
>>
> Reviewed-by: Dan Carpenter <dan.carpenter@linaro.org>
Thanks for reviewing.
>
> But next time, if you're just moving code around, just ignore checkpatch. Do
> the white space changes as a separate patch.
Thanks for the tip, will surely keep this mind.
>
> regards,
> dan carpenter
>
> +- memcpy_to_page(pages[0],
> +- pagelist->offset,
> +- fragments,
> +- head_bytes);
> ++ memcpy_to_page(pages[0], pagelist->offset,
> ++ fragments, head_bytes);
> }
> + if ((actual >= 0) && (head_bytes < actual) &&
> + (tail_bytes != 0))
> + memcpy_to_page(pages[num_pages - 1],
> +- (pagelist->offset + actual) &
> +- (PAGE_SIZE - 1) & ~(drv_mgmt->info->cache_line_size - 1),
> +- fragments + drv_mgmt->info->cache_line_size,
> +- tail_bytes);
> ++ (pagelist->offset + actual) &
> ++ (PAGE_SIZE - 1) & ~(drv_mgmt->info->cache_line_size - 1),
> ++ fragments + drv_mgmt->info->cache_line_size,
> ++ tail_bytes);
>
prev parent reply other threads:[~2024-09-26 4:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 14:21 [PATCH 0/3] staging: vchiq_core: Consolidate bulk xfer helper Umang Jain
2024-09-19 14:21 ` [PATCH 1/3] staging: vchiq_core: Move remote_event_signal() vchiq_core Umang Jain
2024-09-19 14:21 ` [PATCH 2/3] staging: vchiq_core: Move bulk data functions in vchiq_core Umang Jain
2024-09-19 14:21 ` [PATCH 3/3] staging: vchiq_core: Drop vchiq_pagelist.h Umang Jain
2024-09-19 14:26 ` [PATCH 0/3] staging: vchiq_core: Consolidate bulk xfer helper Umang Jain
2024-09-25 9:23 ` Dan Carpenter
2024-09-26 4:10 ` Umang Jain [this message]
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=b7e0d579-a3c5-42ee-a65c-945f5c368124@ideasonboard.com \
--to=umang.jain@ideasonboard.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=wahrenst@gmx.net \
/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