mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	linux-staging@lists.linux.dev, philipp.g.hortmann@gmail.com,
	~lkcamp/patches@lists.sr.ht
Subject: Re: [PATCH v3] staging: rtl8723bs: remove code depending on cflag
Date: Tue, 10 Dec 2024 10:28:48 +0300	[thread overview]
Message-ID: <21d2d3f7-c94a-454b-92b4-2eb6a4be6ce9@stanley.mountain> (raw)
In-Reply-To: <20241209213528.5917-1-rodrigo.gobbi.7@gmail.com>

On Mon, Dec 09, 2024 at 06:33:36PM -0300, Rodrigo Gobbi wrote:
> > The commit message should answer any kind of reasonable questions
> > a review is probably going to ask but it doesn't give any information on
> > this.
> 
> I'll try to improve this for future patches, tks for pointing that out.
> 
> > This commit would easier to review if it were broken up in a different
> > way.
> 
> Ok, in that way, a patch series is the best approach here, right?

I'm not your boss, right?  And I can't tell you what to do and what I'm
suggesting is more work.  If you just want to send patch 1 from the
series instead of all three patches, that's fine.  No one is going to
be annoyed by that.

In patch 1, you would only delete code which is obviously surrounded
by #ifdef DBG_RX_SIGNAL_DISPLAY_RAW_DATA so the case statement would
look like:

	case HAL_DEF_DBG_RX_INFO_DUMP:
		break;

It's basically the same as what you wrote but slightly smaller and
easier to review.  But yeah, we're not going to merge this as-is.

> Despite the changes in the series being dependent on each other in this case.

Yep.  Patchsets are generally dependent on each other.  The rule is that
each patch has to make sense on its own.  You can't break the build.  But
they work on top of each other and they're applied in order.

regards,
dan carpenter

      reply	other threads:[~2024-12-10  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 22:53 Rodrigo Gobbi
2024-12-08 10:27 ` Dan Carpenter
2024-12-09 21:33   ` Rodrigo Gobbi
2024-12-10  7:28     ` 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=21d2d3f7-c94a-454b-92b4-2eb6a4be6ce9@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

all inboxes | Powered by JetHome®