From: Dan Carpenter <error27@gmail.com>
To: Luka Gejak <luka.gejak@linux.dev>
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: Thu, 15 Oct 2026 22:52:29 +0300 [thread overview]
Message-ID: <atEu_ZAyNVxyfbMr@stanley.mountain> (raw)
In-Reply-To: <5f06793dbe846865b7d86f656d27caa1c65732b5@linux.dev>
Ah. In staging, patches are merged on a first come first serve basis
so you are free to ignore any patches which are sent after you sent your
deletion patch. Obviously we're not going to merge fixups to a driver
which has been deleted. If there are patches in the list that were sent
earlier and haven't been reviewed then reply to those.
The rule here is that it's a good idea to search lore before sending
a patch.
https://lore.kernel.org/all/?q=rtw_generate_ie
regards,
dan carpenter
next prev parent reply other threads:[~2026-10-15 19:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 12:06 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 [this message]
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
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
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=atEu_ZAyNVxyfbMr@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 \
/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®