From: Dan Carpenter <error27@gmail.com>
To: Luka Gejak <luka.gejak@linux.dev>, Ping-Ke Shih <pkshih@realtek.com>
Cc: Ethan Tidmore <ethantidmore06@gmail.com>,
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: Fri, 16 Oct 2026 11:11:59 +0300 [thread overview]
Message-ID: <atHcT5GG8zzoH7kk@stanley.mountain> (raw)
In-Reply-To: <dec2320eb01dc6499948a936c94512ddfd47e2a4@linux.dev>
Ah... I didn't realize this patch was applied to a different tree.
#Unexpected.
https://lore.kernel.org/all/7e53bd59b7b146caabebeca4347674c7@realtek.com/
That's a mistake. Staging patches should go through the staging tree
or atleast they should be Acked by the staging maintainer.
So, yes, that's always going to lead to merge issues. Not a super big
deal because the conflicts are simple to resolve.
regards,
dan carpenter
next prev parent reply other threads:[~2026-10-16 8:12 UTC|newest]
Thread overview: 19+ 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
2026-10-15 20:17 ` Luka Gejak
2026-10-16 8:11 ` Dan Carpenter [this message]
2026-10-16 8:21 ` Ping-Ke Shih
2026-10-16 8:23 ` Dan Carpenter
2026-10-16 8:21 ` 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=atHcT5GG8zzoH7kk@stanley.mountain \
--to=error27@gmail.com \
--cc=dennylin0707@gmail.com \
--cc=ethantidmore06@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=luka.gejak@linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=pavankumaryalagada@gmail.com \
--cc=pkshih@realtek.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.