From: Anushka Badhe <anushkabadhe@gmail.com>
To: gregkh@linuxfoundation.org, mchehab@kernel.org
Cc: hansg@kernel.org, andy@kernel.org, sakari.ailus@linux.intel.com,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev,
Anushka Badhe <anushkabadhe@gmail.com>
Subject: [PATCH] staging: atomisp: pci: remove leading whitespace at the start of the line
Date: Tue, 24 Mar 2026 13:40:07 +0530 [thread overview]
Message-ID: <20260324081007.23165-1-anushkabadhe@gmail.com> (raw)
Removed the whitespace at the start of the line to comply with
linux kernel coding style.
Signed-off-by: Anushka Badhe <anushkabadhe@gmail.com>
---
drivers/staging/media/atomisp/pci/system_local.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/atomisp/pci/system_local.c b/drivers/staging/media/atomisp/pci/system_local.c
index a8a93760d5b1..3cf35678383f 100644
--- a/drivers/staging/media/atomisp/pci/system_local.c
+++ b/drivers/staging/media/atomisp/pci/system_local.c
@@ -87,7 +87,7 @@ const hrt_address GP_DEVICE_BASE[N_GP_DEVICE_ID] = {
* so, having multiple base addresses for
* different timers does not help*/
const hrt_address GP_TIMER_BASE =
- (hrt_address)0x0000000000000600ULL;
+ (hrt_address)0x0000000000000600ULL;
/* GPIO */
const hrt_address GPIO_BASE[N_GPIO_ID] = {
--
2.43.0
next reply other threads:[~2026-03-24 8:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 8:10 Anushka Badhe [this message]
2026-03-24 11:50 ` Andy Shevchenko
2026-03-24 11:51 ` Andy Shevchenko
2026-03-24 18:08 ` [PATCH v2] staging: atomisp: pci: fix block comment style and merge split declaration Anushka Badhe
2026-03-24 19:43 ` [PATCH v3] staging: media: " Anushka Badhe
2026-03-25 12:08 ` Andy Shevchenko
2026-03-25 13:24 ` [PATCH v4] staging: media: atomisp: pci: fix split GP_TIMER_BASE declaration Anushka Badhe
2026-03-26 10:48 ` Andy Shevchenko
2026-03-25 8:45 ` [PATCH v2] staging: atomisp: pci: fix block comment style and merge split declaration Greg KH
2026-03-25 9:12 ` Anushka B
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=20260324081007.23165-1-anushkabadhe@gmail.com \
--to=anushkabadhe@gmail.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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
all inboxes | Powered by JetHome®