From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Khadija Kamran <kamrankhadijadj@gmail.com>
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
paskripkin@gmail.com, gregkh@linuxfoundation.org,
outreachy@lists.linux.dev
Subject: Re: [PATCH] Staging: r8188eu: Fixed block comment
Date: Fri, 10 Mar 2023 12:52:55 +0100 [thread overview]
Message-ID: <10238267.qUNvkh4Gvn@suse> (raw)
In-Reply-To: <Y+8p7Hyaf4LhO/Sw@khadija-virtual-machine>
On venerdì 17 febbraio 2023 08:17:00 CET Khadija Kamran wrote:
> Fixed block comment by adding '*' in each line. The Check message was
> shown by using checkpatch.pl script.
>
> Signed-off-by: Khadija Kamran <kamrankhadijadj@gmail.com>
> ---
> drivers/staging/r8188eu/core/rtw_br_ext.c | 19 ++++++++++---------
> 1 file changed, 10 insertions(+), 9 deletions(-)
>
Hi Khadija,
As Greg said this driver is not here any longer. This makes me think that you
forgot at least two things...
1) Please pull and rebase the staging tree every day while working on patches
during this period of the Outreachy project. If you had done so, you would
have noticed that your patch cannot any more be applied.
2) I saw this patch by pure luck because you forgot to Cc the Outreachy list.
Therefore, please don't ever forget to Cc that list. Most mentors don't
subscribe the linux-staging list.
Thanks,
Fabio
P.S.: Please use an imperative tone, both in the subject and in the commit
message. For example this patch could have been written the following way:
staging: axis-fifo: Add "*" to multi-line comment
Add asterisks to each line of a multi-line comment to conform to the Linux
development guidelines. Warning reported by checkpatch.pl.
Signed-off-by: [...]
next prev parent reply other threads:[~2023-03-10 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 7:17 [PATCH] Staging: r8188eu: Fixed block comment Khadija Kamran
2023-02-18 19:11 ` Philipp Hortmann
2023-03-09 9:10 ` Greg KH
2023-03-10 11:52 ` Fabio M. De Francesco [this message]
2023-03-10 12:09 ` Dan Carpenter
2023-03-10 12:25 ` Fabio M. De Francesco
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=10238267.qUNvkh4Gvn@suse \
--to=fmdefrancesco@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=kamrankhadijadj@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=paskripkin@gmail.com \
--cc=phil@philpotter.co.uk \
/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