From: Stefano Brivio <sbrivio@redhat.com>
To: Soumyajit Deb <debsoumyajit100@gmail.com>
Cc: gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com,
manishc@marvell.com, GR-Linux-NIC-Dev@marvell.com
Subject: Re: [Outreachy kernel] Re: [Outreachy] [PATCH 0/3] staging: qlge: Resolve various warnings issued by checkpatch.pl
Date: Wed, 1 Apr 2020 22:58:30 +0200 [thread overview]
Message-ID: <20200401225830.4660f152@elisabeth> (raw)
In-Reply-To: <20200401085810.GA19697@ubuntu>
Hi Soumyajit,
On Wed, 1 Apr 2020 14:28:12 +0530
Soumyajit Deb <debsoumyajit100@gmail.com> wrote:
> On Sat, Mar 28, 2020 at 01:32:51PM +0530, Soumyajit Deb wrote:
> > This patchset resolve coding style and indentation issues reported by
> > checkpatch.pl
> > This patchset add space around various binary operators, remove extra
> > unnecessary blank lines and properly indent a multiline comment for the
> > same file qlge_main.c present under drivers/staging/qlge directory.
> >
> > Soumyajit Deb (3):
> > staging: qlge: Add space around operators
> > staging: qlge: Remove extra blank lines
> > staging: qlge: Properly indent a multiline comment
> >
> > drivers/staging/qlge/qlge_main.c | 30 +++++++++++-------------------
> > 1 file changed, 11 insertions(+), 19 deletions(-)
> >
> > --
> > 2.17.1
>
> I have submitted this patcset on 28 March but I haven't recieved any
> review on this.
> Is there anything wrong with this patchset?
>
> Please let me know, so I can correct them and resend the patches if
> needed.
I haven't reviewed this series because I'm confused. You later sent a
series:
Subject: [Outreachy kernel] [Outreachy] [PATCH 0/2] staging: qlge: Resolve various warnings reported by checkpatch.pl
Date: Wed, 1 Apr 2020 12:21:18 +0530
Message-Id: <20200401065120.17459-1-debsoumyajit100@gmail.com>
...how are those different? Which one should I review?
--
Stefano
next prev parent reply other threads:[~2020-04-01 20:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 8:02 [Outreachy] [PATCH 0/3] staging: qlge: Resolve various warnings issued by checkpatch.pl Soumyajit Deb
2020-03-28 8:02 ` [Outreachy] [PATCH 1/3] staging: qlge: Add space around operators Soumyajit Deb
2020-03-28 8:02 ` [Outreachy] [PATCH 2/3] staging: qlge: Remove extra blank lines Soumyajit Deb
2020-03-28 8:02 ` [Outreachy] [PATCH 3/3] staging: qlge: Properly indent a multiline comment Soumyajit Deb
2020-04-01 8:58 ` [Outreachy] [PATCH 0/3] staging: qlge: Resolve various warnings issued by checkpatch.pl Soumyajit Deb
2020-04-01 9:33 ` Greg KH
2020-04-01 10:33 ` Soumyajit Deb
2020-04-01 20:58 ` Stefano Brivio [this message]
2020-04-02 12:43 ` [Outreachy kernel] " Soumyajit Deb
2020-04-02 23:43 ` Stefano Brivio
2020-04-06 13:19 ` Soumyajit Deb
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=20200401225830.4660f152@elisabeth \
--to=sbrivio@redhat.com \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=debsoumyajit100@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=manishc@marvell.com \
--cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.