From: Stefan Wahren <wahrenst@gmx.net>
To: Umang Jain <umang.jain@ideasonboard.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>
Cc: 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>,
Dan Carpenter <dan.carpenter@linaro.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 5/5] staging: vchiq_core: Locally cache cache_line_size information
Date: Thu, 10 Oct 2024 18:52:21 +0200 [thread overview]
Message-ID: <5ce21c8d-a195-44c8-a37d-5d6f441bf027@gmx.net> (raw)
In-Reply-To: <20241010102250.236545-6-umang.jain@ideasonboard.com>
Am 10.10.24 um 12:22 schrieb Umang Jain:
> Locally cache 'cache_line_size' information in a variable instead of
> repeatedly accessing it from drv_mgmt->info. This helps to reflow lines
> under 80 columns.
>
> No functional change intended in this patch.
>
> Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
> ---
Reviewed-by: Stefan Wahren <wahrenst@gmx.net>
next prev parent reply other threads:[~2024-10-10 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 10:22 [PATCH 0/5] staging: vchiq_core: Improve indentation Umang Jain
2024-10-10 10:22 ` [PATCH 1/5] staging: vchiq_core: Fix white space indentation error Umang Jain
2024-10-10 16:54 ` Stefan Wahren
2024-10-10 10:22 ` [PATCH 2/5] staging: vchiq_core: Indent static_assert on single line Umang Jain
2024-10-10 16:55 ` Stefan Wahren
2024-10-10 10:22 ` [PATCH 3/5] staging: vchiq_core: Reflow long lines to 80 columns Umang Jain
2024-10-11 4:36 ` Greg Kroah-Hartman
2024-10-10 10:22 ` [PATCH 4/5] staging: vchiq_core: Macros indentation fix Umang Jain
2024-10-10 16:50 ` Stefan Wahren
2024-10-11 4:36 ` Greg Kroah-Hartman
2024-10-10 10:22 ` [PATCH 5/5] staging: vchiq_core: Locally cache cache_line_size information Umang Jain
2024-10-10 16:52 ` Stefan Wahren [this message]
2024-10-11 4:39 ` Greg Kroah-Hartman
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=5ce21c8d-a195-44c8-a37d-5d6f441bf027@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@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=umang.jain@ideasonboard.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