From: Dan Carpenter <error27@gmail.com>
To: Archana <craechal@gmail.com>
Cc: drv@mailo.com, linux-staging@lists.linux.dev, gregkh@linuxfoundation.org
Subject: Re: [PATCH 2/2] staging: wlan-ng: remove else statement
Date: Sat, 11 Mar 2023 07:58:51 +0300 [thread overview]
Message-ID: <14be11a8-722c-4520-9e1b-5b147bb3d3fc@kili.mountain> (raw)
In-Reply-To: <a4096cdc-97d1-4265-8ce4-b8021ecf5933@kili.mountain>
On Sat, Mar 11, 2023 at 07:34:25AM +0300, Dan Carpenter wrote:
> On Fri, Mar 10, 2023 at 08:59:17PM +0000, Archana wrote:
> > else block is not needed if j is set to -1
> > before if block
> >
> > Signed-off-by: Archana <craechal@gmail.com>
> > ---
>
> Is Archana your full legal name that you would write on a legal document?
Ah, never mind. Apparently this policy has been updated. Pseudonyms
are allowed for people concerned about privacy but anonymous
contributions are not allowed.
https://lore.kernel.org/all/ZAoMxSPKNLoLg7Wl@aschofie-mobl2/
regards,
dan carpenter
next prev parent reply other threads:[~2023-03-11 4:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 20:59 [PATCH 1/2] staging: wlan-ng: remove unnecessary kfree statements Archana
2023-03-10 20:59 ` [PATCH 2/2] staging: wlan-ng: remove else statement Archana
2023-03-11 4:34 ` Dan Carpenter
2023-03-11 4:58 ` Dan Carpenter [this message]
2023-03-11 7:39 ` Greg KH
2023-03-11 12:12 ` [PATCH v2 1/2] staging: wlan-ng: small cleanup in writeimage() Archana
2023-03-11 12:12 ` [PATCH v2 2/2] staging: wlan-ng: small cleanup in plugimage() Archana
2023-03-11 12:37 ` [PATCH v2 1/2] staging: wlan-ng: small cleanup in writeimage() Dan Carpenter
2023-03-11 12:45 ` [PATCH 2/2] staging: wlan-ng: remove else statement Archana
2023-03-11 7:40 ` [PATCH 1/2] staging: wlan-ng: remove unnecessary kfree statements Greg KH
2023-03-16 11:19 ` Archana
2023-03-16 11:27 ` Archana
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=14be11a8-722c-4520-9e1b-5b147bb3d3fc@kili.mountain \
--to=error27@gmail.com \
--cc=craechal@gmail.com \
--cc=drv@mailo.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).