From: Julia Lawall <julia.lawall@inria.fr>
To: jovial umwari <umwarijovial@gmail.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: [PATCH] WARNING: Possible repeated word: 'very'
Date: Sat, 29 Oct 2022 19:35:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2210291934400.2917@hadrien> (raw)
In-Reply-To: <CAMk1CBOgUPjeMw9NmCthsQsDJXY8U4WCBTmNi-3h_BroGnh_QQ@mail.gmail.com>
On Sat, 29 Oct 2022, jovial umwari wrote:
> Noted. Thank you sir
Please don't top post. Your reponse should appear below the text that you
are responding to.
julia
>
> On Fri, 28 Oct 2022 at 21:35, Alison Schofield
> <alison.schofield@intel.com> wrote:
> >
> > On Fri, Oct 28, 2022 at 08:14:20AM +0300, UMWARI JOVIAL wrote:
> > > i used checkpatch.pl script to identify the above
> > > Repetition of the same word in one sentence same line
> > >
> > > Signed-off-by: UMWARI JOVIAL <umwarijovial@gmail.com>
> >
> > This is my (not yet automated) response:
> >
> > You are sending patches to the Outreachy list, in a way
> > that makes me suspect you have overlooked the Outreachy
> > Project Contribution Information.
> >
> > Please review:
> > https://www.outreachy.org/outreachy-december-2022-internship-round/communities/linux-kernel/ (only accepted applicants can see this link)
> >
> > https://lore.kernel.org/outreachy/Y0D+dzbjRtuc0KT4@aschofie-mobl2/
> >
> > Alison
> >
> > > ---
> > > drivers/staging/rtl8712/rtl871x_xmit.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/staging/rtl8712/rtl871x_xmit.c b/drivers/staging/rtl8712/rtl871x_xmit.c
> > > index 090345bad223..30a0276b8b58 100644
> > > --- a/drivers/staging/rtl8712/rtl871x_xmit.c
> > > +++ b/drivers/staging/rtl8712/rtl871x_xmit.c
> > > @@ -766,7 +766,7 @@ void r8712_free_xmitbuf(struct xmit_priv *pxmitpriv, struct xmit_buf *pxmitbuf)
> > > * If we turn on USE_RXTHREAD, then, no need for critical section.
> > > * Otherwise, we must use _enter/_exit critical to protect free_xmit_queue...
> > > *
> > > - * Must be very very cautious...
> > > + * Must be very cautious...
> > > *
> > > */
> > > struct xmit_frame *r8712_alloc_xmitframe(struct xmit_priv *pxmitpriv)
> > > --
> > > 2.25.1
> > >
> > >
>
>
prev parent reply other threads:[~2022-10-29 17:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 5:14 UMWARI JOVIAL
2022-10-28 6:08 ` Greg KH
2022-10-28 6:13 ` jovial umwari
2022-10-28 6:28 ` Greg KH
2022-10-28 9:53 ` jovial umwari
2022-10-28 18:35 ` Alison Schofield
2022-10-29 16:51 ` jovial umwari
2022-10-29 17:35 ` Julia Lawall [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=alpine.DEB.2.22.394.2210291934400.2917@hadrien \
--to=julia.lawall@inria.fr \
--cc=alison.schofield@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=umwarijovial@gmail.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®