Remove trailing whitespace to comply with kernel coding style.

Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Gabriel Shahrouzi <gshahrouzi@gmail.com>
---
Changes in v2:
	- Resend using git send-email to fix formatting issues in email body.
Changes in v3:
	- Fix indent level of diff.
---
 drivers/staging/rtl8723bs/include/hal_pwr_seq.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/rtl8723bs/include/hal_pwr_seq.h b/drivers/staging/rtl8723bs/include/hal_pwr_seq.h
index b93d74a5b9a5..48bf7f66a06e 100644
--- a/drivers/staging/rtl8723bs/include/hal_pwr_seq.h
+++ b/drivers/staging/rtl8723bs/include/hal_pwr_seq.h
@@ -209,7 +209,7 @@
 #define RTL8723B_TRANS_END															\
 	/* format */																\
 	/* { offset, cut_msk, fab_msk|interface_msk, base|cmd, msk, value }, comments here*/								\
-	{0xFFFF, PWR_CUT_ALL_MSK, PWR_FAB_ALL_MSK, PWR_INTF_ALL_MSK, 0, PWR_CMD_END, 0, 0}, 
+	{0xFFFF, PWR_CUT_ALL_MSK, PWR_FAB_ALL_MSK, PWR_INTF_ALL_MSK, 0, PWR_CMD_END, 0, 0},
 
 
 extern struct wlan_pwr_cfg rtl8723B_power_on_flow[RTL8723B_TRANS_CARDEMU_TO_ACT_STEPS+RTL8723B_TRANS_END_STEPS];
-- 
2.43.0

On Thu, Apr 03, 2025 at 12:08:07PM -0400, Gabriel Shahrouzi wrote:
> Remove trailing whitespace to comply with kernel coding style.
> 
> Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

As far as I can recall, I did not suggest this patch :(

On Fri, Apr 4, 2025 at 2:28 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Thu, Apr 03, 2025 at 12:08:07PM -0400, Gabriel Shahrouzi wrote:
> > Remove trailing whitespace to comply with kernel coding style.
> >
> > Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> As far as I can recall, I did not suggest this patch :(
Whoops. I misunderstood. I initially thought "it" meant the suggestion
for the new patch revision. But thinking more about it, that would be
redundant, since that information already exists in the previous
version's thread and could be spammy with many reviewers.

However, providing information on how that idea first came up is
useful, since that origin story doesn't already exist on the thread
(countering the base assumption that you alone came up with it).

Separately, I need to make sure to use the official documentation for
tags instead of relying on Google searches and third-party
documentation.