public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Luka Gejak <luka.gejak@linux.dev>
To: Prithvi <activprithvi@gmail.com>
Cc: gregkh@linuxfoundation.org, abrahamadekunle50@gmail.com,
	b9788213@gmail.com, straube.linux@gmail.com,
	tmimiharoen@gmail.com, filippo.muschera@gmail.com,
	ethantidmore06@gmail.com, andriy.shevchenko@linux.intel.com,
	rayfraytech@gmail.com, david@cardinalsystem.net,
	weibu@redadmin.org, dharanitharan725@gmail.com,
	ignacio.pena87@gmail.com, dan.carpenter@linaro.org,
	karanja99erick@gmail.com, khushalchitturi@gmail.com,
	suunj1331@gmail.com, s9430939@naver.com, nikolayof23@gmail.com,
	bryant.boatright@proton.me, ysinghcin@gmail.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
	david.hunter.linux@gmail.com, khalid@kernel.org
Subject: Re: [PATCH v4 0/5] staging: rtl8723bs: Code cleanup in drivers/staging/rtl8723bs
Date: Thu, 09 Apr 2026 16:57:20 +0200	[thread overview]
Message-ID: <2AEE6A74-3C08-45A6-BA28-55BDE5072EC5@linux.dev> (raw)
In-Reply-To: <20260409145045.44r4f5bleklkk4ha@inspiron>

On April 9, 2026 4:50:45 PM GMT+02:00, Prithvi <activprithvi@gmail.com> wrote:
>On Thu, Apr 09, 2026 at 04:18:28PM +0200, Luka Gejak wrote:
>> On Thu Apr 9, 2026 at 3:50 PM CEST, Prithvi Tambewagh wrote:
>> > This patch series focuses on code cleanup in drivers/staging/rtl8723bs,
>> > majorly focusing on fixing checkpatch warnings of constant being on right
>> > side of test in comparisons, deletion of empty if block ,use of
>> > read_poll_timeout_atomic(), and other code simplifications.
>> >
>> > Changes since v3:
>> > - Rebased the patches on top of staging-next
>> > - Remove compilation output from cover letter
>> > - Add changes in each patch version in cover letter
>> >
>> > v3 link: https://lore.kernel.org/linux-staging/1D11A73B-4869-47DB-B8F5-FB3F0D7FF932@linux.dev/T/#m3190af744bc1e1f151e9e8503c7d20951fe27534
>> 
>> ...
>> 
>> Hi Prithvi,
>> this seems better, but I have one question. Did patch series appear on 
>> mailing list to you, because I cant find it and my emails sent today 
>> don't appear either. Not to be misunderstood I don't believe this is 
>> your fault but I would like to know if you are experiencing the same 
>> problem.
>> Best regards,
>> Luka Gejak
>
>Hi Luka,
>
>I just observed I am also facing the same issue - I am not able to see the 
>patch series on the mailing list, no idea why :( However I received the 
>sent patches as well as your reviewed by tags on mail but I am not sure why 
>the patch series is not visible on the mailing list.
>
>Shall I resend the patch series?
>
>Best Reagrds,
>Prithvi

Not necessarily, that is probably caused by mailing list lagging 
behind, so let's just wait and see(it should stop lagging in some 
time). Patches as well as reviews should appear then. Also, did you 
receive two emails per patch from me or one because my email client is
saying two.
Best regards,
Luka Gejak

  reply	other threads:[~2026-04-09 14:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 13:50 [PATCH v4 0/5] staging: rtl8723bs: Code cleanup in drivers/staging/rtl8723bs Prithvi Tambewagh
2026-04-09 13:50 ` [PATCH v4 1/5] staging: rtl8723bs: move constant to right side of test in comparison Prithvi Tambewagh
2026-04-09 14:10   ` Luka Gejak
2026-04-09 13:50 ` [PATCH v4 2/5] staging: rtl8723bs: remove empty if statement block Prithvi Tambewagh
2026-04-09 14:10   ` Luka Gejak
2026-04-09 13:50 ` [PATCH v4 3/5] staging: rtl8723bs: simplify boolean return in IsFrameTypeCtrl() Prithvi Tambewagh
2026-04-09 14:10   ` Luka Gejak
2026-04-09 13:50 ` [PATCH v4 4/5] staging: rtl8723bs: use read_poll_timeout_atomic in _is_fw_read_cmd_down Prithvi Tambewagh
2026-04-09 14:10   ` Luka Gejak
2026-04-09 13:50 ` [PATCH v4 5/5] staging: rtl8723bs: remove duplicate rate checks in PHY_GetTxPowerIndexBase() Prithvi Tambewagh
2026-04-09 14:14   ` Luka Gejak
2026-04-09 14:18 ` [PATCH v4 0/5] staging: rtl8723bs: Code cleanup in drivers/staging/rtl8723bs Luka Gejak
2026-04-09 14:50   ` Prithvi
2026-04-09 14:57     ` Luka Gejak [this message]
2026-04-09 15:30       ` Prithvi
2026-04-09 15:32         ` Luka Gejak
2026-04-09 15:42           ` Luka Gejak
2026-04-09 15:02     ` Greg KH
2026-04-09 15:39       ` Prithvi
2026-04-09 15:44         ` Luka Gejak
2026-04-09 15:55           ` Andy Shevchenko

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=2AEE6A74-3C08-45A6-BA28-55BDE5072EC5@linux.dev \
    --to=luka.gejak@linux.dev \
    --cc=abrahamadekunle50@gmail.com \
    --cc=activprithvi@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=b9788213@gmail.com \
    --cc=bryant.boatright@proton.me \
    --cc=dan.carpenter@linaro.org \
    --cc=david.hunter.linux@gmail.com \
    --cc=david@cardinalsystem.net \
    --cc=dharanitharan725@gmail.com \
    --cc=ethantidmore06@gmail.com \
    --cc=filippo.muschera@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ignacio.pena87@gmail.com \
    --cc=karanja99erick@gmail.com \
    --cc=khalid@kernel.org \
    --cc=khushalchitturi@gmail.com \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=nikolayof23@gmail.com \
    --cc=rayfraytech@gmail.com \
    --cc=s9430939@naver.com \
    --cc=skhan@linuxfoundation.org \
    --cc=straube.linux@gmail.com \
    --cc=suunj1331@gmail.com \
    --cc=tmimiharoen@gmail.com \
    --cc=weibu@redadmin.org \
    --cc=ysinghcin@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