public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Fabio Aiuto <fabioaiuto83@gmail.com>
Cc: gregkh@linuxfoundation.org, joe@perches.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 16/30] staging: rtl8723bs: tidy up some error handling in core/rtw_mlme.c
Date: Sat, 3 Apr 2021 13:04:34 +0300	[thread overview]
Message-ID: <20210403100434.GX2065@kadam> (raw)
In-Reply-To: <20210403095029.GD1563@agape.jhs>

On Sat, Apr 03, 2021 at 11:50:30AM +0200, Fabio Aiuto wrote:
> On Sat, Apr 03, 2021 at 11:42:47AM +0200, Fabio Aiuto wrote:
> > On Sat, Apr 03, 2021 at 11:13:38AM +0200, Fabio Aiuto wrote:
> > > the RT_TRACE() output is not useful so we want to delete it. In this case
> > > there is no cleanup for rtw_cleanbss_cmd() required or even possible. I've
> > > deleted the RT_TRACE() output and added a goto unlock to show
> > > that we can't continue if rtw_createbss_cmd() fails.
> > > 
> > > Suggested-by: David Carpenter <dan.carpenter@oracle.org>
> > > Signed-off-by: Fabio Aiuto <fabioaiuto83@gmail.com>
> > > ---
> > >  drivers/staging/rtl8723bs/core/rtw_mlme.c | 17 +++++++++++------
> > >  1 file changed, 11 insertions(+), 6 deletions(-)
> > 
> > Hi Dan,
> > 
> > I put a Suggested-by tag on one patch in v3 patchset. But reading the docs
> > on submitting patches I relaized later that maybe it requires your permission before.
> > 
> > It' written about Reviewed-by but not about Suggested-by, should I have asked you before, should I?
> > 
> > I'm sorry if I should have.
> 
> Found it, I'm really sorry
> 
> A Suggested-by: tag indicates that the patch idea is suggested by the person
> named and ensures credit to the person for the idea. Please note that this
> tag should not be added without the reporter's permission, especially if the
> idea was not posted in a public forum. That said, if we diligently credit our
> idea reporters, they will, hopefully, be inspired to help us again in the
> future.
> 
> I wonder if in the case of this patch was needed this tag..

Yeah, it's fine.  It's all on a public list so it's not a secret.

regards,
dan carpenter


  reply	other threads:[~2021-04-03 10:04 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03  9:13 [PATCH v3 00/30] staging: rtl8723bs: remove RT_TRACE logs in core/* Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 01/30] staging: rtl8723bs: remove RT_TRACE logs in core/rtw_xmit.c Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 02/30] staging: rtl8723bs: fix condition in if statement " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 03/30] staging: rtl8723bs: remove RT_TRACE logs in core/rtw_security.c Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 04/30] staging: rtl8723bs: fix line exceed warning " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 05/30] staging: rtl8723bs: fix spaces around operator issues " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 06/30] staging: rtl8723bs: remove all RT_TRACE logs in core/rtw_eeprom.c Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 07/30] staging: rtl8723bs: fix error prone if conditions " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 08/30] staging: rtl8723bs: remove all RT_TRACE logs in core/rtw_pwrctrl.c Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 09/30] staging: rtl8723bs: fix logical continuation issue " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 10/30] staging: rtl8723bs: remove unnecessary parentheses in if-condition " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 11/30] staging: rtl8723bs: remove RT_TRACE logs in core/rtw_cmd.c Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 12/30] staging: rtl8723bs: fix null check conditions " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 13/30] staging: rtl8723bs: remove unnecessary parentheses in if condition " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 14/30] staging: rtl8723bs: remove commented RT_TRACE calls in core/rtw_mlme.c Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 15/30] staging: rtl8723bs: remove RT_TRACE logs " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 16/30] staging: rtl8723bs: tidy up some error handling " Fabio Aiuto
2021-04-03  9:42   ` Fabio Aiuto
2021-04-03  9:50     ` Fabio Aiuto
2021-04-03 10:04       ` Dan Carpenter [this message]
2021-04-03  9:13 ` [PATCH v3 17/30] staging: rtl8723bs: remove RT_TRACE logs in core/rtw_mlme_ext.c Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 18/30] staging: rtl8723bs: remove commented RT_TRACE calls in core/rtw_recv.c Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 19/30] staging: rtl8723bs: remove RT_TRACE logs " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 20/30] staging: rtl8723bs: added spaces around operator " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 21/30] staging: rtl8723bs: split long line " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 22/30] staging: rtl8723bs: remove unnecessary parentheses " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 23/30] staging: rtl8723bs: fix comparison in if condition " Fabio Aiuto
2021-04-03 15:24   ` Joe Perches
2021-04-03  9:13 ` [PATCH v3 24/30] staging: rtl8723bs: remove commented RT_TRACE call in core/rtw_ioctl_set.c Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 25/30] staging: rtl8723bs: remove RT_TRACE logs " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 26/30] staging: rtl8723bs: place constant on the right side of the test " Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 27/30] staging: rtl8723bs: remove all RT_TRACE logs in core/rtw_wlan_util.c Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 28/30] staging: rtl8723bs: remove RT_TRACE logs in core/rtw_sta_mgt.c Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 29/30] staging: rtl8723bs: remove RT_TRACE logs in core/rtw_ieee80211.c Fabio Aiuto
2021-04-03  9:13 ` [PATCH v3 30/30] staging: rtl8723bs: add spaces around operators " Fabio Aiuto
2021-04-03 15:02 ` [PATCH v3 00/30] staging: rtl8723bs: remove RT_TRACE logs in core/* Joe Perches
2021-04-03 15:21   ` Fabio Aiuto
2021-04-03 16:17     ` Joe Perches
2021-04-03 17:28       ` Fabio Aiuto
2021-04-03 20:02         ` Joe Perches
2021-04-04  6:48           ` Fabio Aiuto

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=20210403100434.GX2065@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=fabioaiuto83@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.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