From: Dan Carpenter <dan.carpenter@linaro.org>
To: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>
Cc: gregkh@linuxfoundation.org, philipp.g.hortmann@gmail.com,
~lkcamp/patches@lists.sr.ht, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] staging: rtl8723bs: remove code depending on cflag
Date: Thu, 12 Dec 2024 08:42:28 +0300 [thread overview]
Message-ID: <2eba9c05-4efc-4060-8cdf-26f701ba9794@stanley.mountain> (raw)
In-Reply-To: <20241211233415.37702-1-rodrigo.gobbi.7@gmail.com>
On Wed, Dec 11, 2024 at 08:26:38PM -0300, Rodrigo Gobbi wrote:
> The proposal is to remove the code isolated with DBG_RX_SIGNAL_DISPLAY_RAW_DATA and
> all the related code since it was not compiling and there is no information about it's usage.
>
> v5 is just joining 2th and 3th patches from v4.
> Tks again and regards.
> ---
> Changelog
> v4: https://lore.kernel.org/linux-staging/20241210210741.17101-1-rodrigo.gobbi.7@gmail.com/
> v3: https://lore.kernel.org/linux-staging/20241206230110.11893-1-rodrigo.gobbi.7@gmail.com/
> v2: https://lore.kernel.org/lkml/20241125225308.8702-1-rodrigo.gobbi.7@gmail.com/t/#mf22f30a9c689bd793988d7e7a58c0b119206116c
> v1: https://lore.kernel.org/linux-staging/2024112500-authentic-primarily-b5da@gregkh/T/#mea4fba3775a1015f345dfe322854c55db0cddf43
Perfect. Thanks!
Reviewed-by: Dan Carpenter <dan.carpenter@linaro.org>
regards,
dan carpenter
prev parent reply other threads:[~2024-12-12 5:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 23:26 [PATCH v5 0/2] staging: rtl8723bs: remove code depending on cflag Rodrigo Gobbi
2024-12-11 23:26 ` [PATCH v5 1/2] staging: rtl8723bs: delete DBG_RX_SIGNAL_DISPLAY_RAW_DATA ifdef code Rodrigo Gobbi
2024-12-11 23:26 ` [PATCH v5 2/2] staging: rtl8723bs: delete HAL_DEF_DBG_RX_INFO_DUMP enum and caller Rodrigo Gobbi
2024-12-12 5:42 ` Dan Carpenter [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=2eba9c05-4efc-4060-8cdf-26f701ba9794@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@gmail.com \
--cc=rodrigo.gobbi.7@gmail.com \
--cc=~lkcamp/patches@lists.sr.ht \
/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