All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Fabio Aiuto <fabioaiuto83@gmail.com>
Cc: devel@driverdev.osuosl.org, linux.kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] staging: rtl8723bs: remove unused code blocks
Date: Fri, 12 Mar 2021 17:17:49 +0100	[thread overview]
Message-ID: <YEuULYAjcVOo5Cyr@kroah.com> (raw)
In-Reply-To: <cover.1615561446.git.fabioaiuto83@gmail.com>

On Fri, Mar 12, 2021 at 04:49:40PM +0100, Fabio Aiuto wrote:
> This patch set removes unused code blocks as required in
> TODO file:
> 
>     find and remove code blocks guarded by never set CONFIG_FOO defines
> 
> Fabio Aiuto (3):
>   staging: rtl8723bs: remove unused code blocks
>   staging: rtl8723bs: remove unused code blocks
>   staging: rtl8723bs: remove unused code blocks

You sent 3 patches that did different things, yet had identical subject
lines :(

Please fix up and make them unique.

thanks,

greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

      parent reply	other threads:[~2021-03-12 16:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 15:49 [PATCH 0/3] staging: rtl8723bs: remove unused code blocks Fabio Aiuto
2021-03-12 16:04 ` Fabio Aiuto
2021-03-12 16:04 ` Fabio Aiuto
2021-03-12 15:50 ` [PATCH 1/3] " Fabio Aiuto
2021-03-12 16:06   ` Fabio Aiuto
2021-03-12 16:06   ` Fabio Aiuto
2021-03-12 15:52 ` [PATCH 2/3] " Fabio Aiuto
2021-03-12 16:07   ` Fabio Aiuto
2021-03-12 16:07   ` Fabio Aiuto
2021-03-12 15:58 ` [PATCH 3/3] " Fabio Aiuto
2021-03-12 16:10   ` Fabio Aiuto
2021-03-12 16:10   ` Fabio Aiuto
2021-03-12 15:58   ` Fabio Aiuto
2021-03-12 16:17 ` Greg KH [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=YEuULYAjcVOo5Cyr@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=fabioaiuto83@gmail.com \
    --cc=linux.kernel@vger.kernel.org \
    /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.