All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mirza Ishan Beg <seedandsyntax@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	 nikolayof23@gmail.com, lkp@intel.com
Subject: Re: [PATCH v4] staging: rtl8723bs: refactor traffic_stat access in collect_traffic_statistics
Date: Sat, 29 Aug 2026 20:52:24 +0530	[thread overview]
Message-ID: <apLzDlcfiu9NJUwc@Debian.myguest.virtualbox.org> (raw)
In-Reply-To: <2026082546-treble-delivery-49dc@gregkh>

On 26/08/25 05:43PM, Greg KH wrote:
> Where is the 1-3 version info?
> 
> And the "Closes:" isn't correct, 0-day was responding to previous errors
> you made in other versions of this series, not the original code.
> THere's nothing wrong with the original code that needs to be "Closed".
> 
> thanks,
> 
> greg k-h

I see, thanks for the feedback. I will prepare v5 with a complete
changelog covering v1 to v5, and I will remove the Reported-by and
Closes tags for the reasons stated: those errors were introduced from my own
earlier patch versions. I'll send v5 shortly.

Regards,
Mirza Ishan Beg 


  reply	other threads:[~2026-08-29 15:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 14:48 [PATCH] staging: rtl8723bs: refactor traffic_stat access in collect_traffic_statistics Mirza Ishan Beg
2026-08-03 15:09 ` Greg KH
2026-08-03 15:43   ` Mirza Ishan Beg
2026-08-03 15:46     ` Greg KH
2026-08-03 16:00 ` [PATCH v2] " Mirza Ishan Beg
2026-08-03 18:03   ` [PATCH v3] " Mirza Ishan Beg
2026-08-07 15:05     ` [PATCH v4] " Mirza Ishan Beg
2026-08-25 15:43       ` Greg KH
2026-08-29 15:22         ` Mirza Ishan Beg [this message]
2026-08-29 15:48       ` [PATCH v5] " Mirza Ishan Beg
2026-08-06 17:15 ` [PATCH] " kernel test robot
2026-08-06 22:04 ` kernel test robot

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=apLzDlcfiu9NJUwc@Debian.myguest.virtualbox.org \
    --to=seedandsyntax@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=lkp@intel.com \
    --cc=nikolayof23@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 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.