[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <58a34e59c75e2f9fbb918d632590f3115a585bfc.camel@zohomail.com>
Date: Sun, 23 Oct 2022 16:05:50 +0700
From: Aaron Lawrence <t4rmin@...omail.com>
To: Nam Cao <namcaov@...il.com>
Cc: gregkh@...uxfoundation.org, linux-staging@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] Staging: rtl8192e: rtl819x_HTProc: fixed missing
blank space
On Sat, 2022-10-22 at 20:21 +0200, Nam Cao wrote:
> On Sat, Oct 22, 2022 at 10:48:08PM +0700, Aaron Lawrence wrote:
> > > From e6635103e3cf2426220767955b99d2e2b62a7329 Mon Sep 17 00:00:00 2001
> > Message-Id: <e6635103e3cf2426220767955b99d2e2b62a7329.1666450553.git.t4rmin@...omail.com>
> > In-Reply-To: <cover.1666450553.git.t4rmin@...omail.com>
> > References: <cover.1666450553.git.t4rmin@...omail.com>
> > From: Aaron Lawrence <t4rmin@...omail.com>
> > Date: Sat, 22 Oct 2022 20:46:25 +0700
>
> I think you messed up something here. These are not supposed to be in
> the email description. All your patches are sent separatedly, instead of
> being in the same thread.
>
> I can recommend follow the instructions in this website:
> https://kernelnewbies.org/FirstKernelPatch
>
> > Subject: [PATCH 1/3] Staging: rtl8192e: rtl819x_HTProc: fixed missing blank
> > space
> >
> > Added a missing blank space as per the Linux kernel coding-style
> > regulations. The issue was flagged by the checkpatch script as a
> > warning.
> >
> > Signed-off-by: Aaron Lawrence <t4rmin@...omail.com>
> > ---
> > drivers/staging/rtl8192e/rtl819x_HTProc.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c b/drivers/staging/rtl8192e/rtl819x_HTProc.c
> > index ef3dca51cf99..b763cf0ba356 100644
> > --- a/drivers/staging/rtl8192e/rtl819x_HTProc.c
> > +++ b/drivers/staging/rtl8192e/rtl819x_HTProc.c
> > @@ -70,6 +70,7 @@ static u8 LINKSYS_MARVELL_4400N[3] = {0x00, 0x14, 0xa4};
> > void HTUpdateDefaultSetting(struct rtllib_device *ieee)
> > {
> > struct rt_hi_throughput *pHTInfo = ieee->pHTInfo;
> > +
> > pHTInfo->bRegShortGI20MHz = 1;
> > pHTInfo->bRegShortGI40MHz = 1;
> > --
> > 2.38.1
> >
> >
Ah, I see. I (hopefully) will be sending the correct email
patchset format next time. Thanks.
Aaron
Powered by blists - more mailing lists