From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Dan Carpenter" <error27@gmail.com>,
"Ethan Tidmore" <ethantidmore06@gmail.com>
Cc: pavankumaryalagada@gmail.com, gregkh@linuxfoundation.org,
outreachy@lists.linux.dev, dennylin0707@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: remove unnecessary parentheses
Date: Thu, 15 Oct 2026 20:11:02 +0000 [thread overview]
Message-ID: <672f78b36290a4021d3f94d9ec401d23420febbc@linux.dev> (raw)
In-Reply-To: <atEtUV5q9MHRSTJb@stanley.mountain>
October 15, 2026 at 9:45 PM, "Dan Carpenter" <error27@gmail.com> wrote:
>
> On Thu, Oct 15, 2026 at 10:41:53AM -0500, Ethan Tidmore wrote:
>
> >
> > On Thu Oct 15, 2026 at 9:11 AM CDT, Luka Gejak wrote:
> > October 15, 2026 at 2:06 PM, pavankumaryalagada@gmail.com wrote:
> >
> >
> > From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
> >
> > Remove redundant parentheses around the address-of operator to
> > follow kernel coding style.
> >
> > Signed-off-by: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
> > ---
> >
> > Hi Yalagada,
> >
> > I'm just letting you know that this change is no longer needed as the
> > entire staging/rtl8723bs driver is being deprecated and removed.
> > Support for RTL8723BS has been ported to rtw88 subsystem.
> >
> > So rtl8723bs patches aren't being accepted anymore? I saw Dan reviewing
> > one earlier, just wondering.
> >
> I didn't know it was being removed. My expectation is that we'll
> probably keep merging patches until it's actually removed. It's sometimes
> easier to just merge easy uncontroversial things without trying to track
> everything happening in the kernel. We should obviously delete the driver
> as soon as the other patch is merged.
>
> regards,
> dan carpenter
>
But won't that cause a conflict? PR has been sent today, carrying my
patch that removes whole staging/rtl8723bs into net-next and if
another patch is merged into staging-next, whose time of commit is
later than the time I made my commit localy it will try to exit a
non-existent file.
And since both net-next tree and staging-next tree are merged at the
same merge window this will cause merge conflict. Correct me if I am
wrong, but this is what I think would happen.
Best regards,
Luka Gejak
next prev parent reply other threads:[~2026-10-15 20:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 12:06 [PATCH] staging: rtl8723bs: remove unnecessary parentheses pavankumaryalagada
2026-10-15 14:11 ` Luka Gejak
2026-10-15 15:31 ` Jeremy Clifton
2026-10-15 15:31 ` Yalagada Pavan Kumar
2026-10-15 15:41 ` Ethan Tidmore
2026-10-15 15:57 ` Luka Gejak
2026-10-15 19:52 ` Dan Carpenter
2026-10-15 20:14 ` Luka Gejak
2026-10-15 19:45 ` Dan Carpenter
2026-10-15 20:11 ` Luka Gejak [this message]
2026-10-15 20:17 ` Luka Gejak
-- strict thread matches above, loose matches on Subject: below --
2026-05-30 3:16 Eugene Mavick
2026-02-22 7:26 Yan Pan
2026-01-29 22:17 Siwanan Bungtong
2025-12-04 11:53 [PATCH] staging: rtl8723bs: Remove " Nazar Kletskii
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=672f78b36290a4021d3f94d9ec401d23420febbc@linux.dev \
--to=luka.gejak@linux.dev \
--cc=dennylin0707@gmail.com \
--cc=error27@gmail.com \
--cc=ethantidmore06@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=pavankumaryalagada@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