mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Eric LI (Honggang)" <eric.lee0305@gmail.com>,
	Hungyu Lin <dennylin0707@gmail.com>,
	Andrei Khomenkov <khomenkov@mailbox.org>,
	Khushal Chitturi <khushalchitturi@gmail.com>,
	Ethan Tidmore <ethantidmore06@gmail.com>,
	Oskar Ray-Frayssinet <rayfraytech@gmail.com>,
	SeungJu Cheon <suunj1331@gmail.com>,
	Dalvin-Ehinoma Noah Aiguobas <fliegbert2@gmail.com>,
	Jennifer Guo <guojy.bj@gmail.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: refactor xmit_xmitframe
Date: Thu, 1 Oct 2026 13:42:33 +0300	[thread overview]
Message-ID: <ar45GeQXJ-dIUw91@stanley.mountain> (raw)
In-Reply-To: <2026100121-chirpy-stomp-9fbe@gregkh>

On Thu, Oct 01, 2026 at 11:34:30AM +0200, Greg Kroah-Hartman wrote:
> > +					if (pxmitbuf->len > 0 &&
> > +					    pxmitbuf->priv_data) {
> > +						struct xmit_frame *pframe;
> > +
> > +						pframe = (struct xmit_frame *)pxmitbuf->priv_data;
> > +						pframe->agg_num = k;
> > +						pxmitbuf->agg_num = k;
> > +						rtl8723b_update_txdesc(pframe, pframe->buf_addr);
> > +						rtw_free_xmitframe(pxmitpriv, pframe);
> > +						pxmitbuf->priv_data = NULL;
> > +						enqueue_pending_xmitbuf(pxmitpriv, pxmitbuf);
> > +						/* can not yield under lock */
> > +						/* yield(); */
> > +					} else
> > +						rtw_free_xmitbuf(pxmitpriv, pxmitbuf);
> > +
> > +					pxmitbuf = NULL;
> 
> This jumped out at me, why add this new line?
> 

The patch is correct but the new version is as confusing as heck...
Glad that I'm not the only person who thinks this.  I've been doing
more and more AI coding these days and they say that AI makes you
stupid so I was worried about my own brain health.

regards,
dan carpenter

  reply	other threads:[~2026-10-01 10:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 15:16 Eric LI (Honggang)
2026-10-01  9:34 ` Greg Kroah-Hartman
2026-10-01 10:42   ` Dan Carpenter [this message]
2026-10-01 15:28   ` Eric Lee

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=ar45GeQXJ-dIUw91@stanley.mountain \
    --to=error27@gmail.com \
    --cc=dennylin0707@gmail.com \
    --cc=eric.lee0305@gmail.com \
    --cc=ethantidmore06@gmail.com \
    --cc=fliegbert2@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=guojy.bj@gmail.com \
    --cc=khomenkov@mailbox.org \
    --cc=khushalchitturi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=rayfraytech@gmail.com \
    --cc=suunj1331@gmail.com \
    /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®