The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Nikolay Kulikov <nikolayof23@gmail.com>
To: Dan Carpenter <error27@gmail.com>
Cc: PRAMOD MAURYA <pramod.nexgen@gmail.com>,
	gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Ethan Tidmore <ethantidmore06@gmail.com>,
	Yuvraj Singh Chauhan <ysinghcin@gmail.com>,
	Bryant Boatright <bryant.boatright@proton.me>
Subject: Re: [PATCH] staging: rtl8723bs: Fix coding style in ieee80211.h
Date: Mon, 11 May 2026 15:55:26 +0300	[thread overview]
Message-ID: <agHRvlftXepSzPDJ@archlinux> (raw)
In-Reply-To: <agGYe8_ggP5aQHha@stanley.mountain>

On Mon, May 11, 2026 at 11:51:07AM +0300, Dan Carpenter wrote:
> On Sun, May 10, 2026 at 09:04:14PM +0300, Nikolay Kulikov wrote:
> > On Sun, May 10, 2026 at 10:48:22PM +0530, PRAMOD MAURYA wrote:
> > > Hi Nikolay,
> > > 
> > > Thanks for the review.
> > > 
> > > Understood. I’ll split the changes into separate logical patches and keep
> > > future submissions more focused.
> > > 
> > > The Cc list was generated using get_maintainer.pl. I’ll review it more
> > > carefully before sending the next revision.
> > 
> > Run this script with the '--nogit-fallback' flag, it will not output the
> > developers who modified this file, only the maintainer and mailing
> > lists.
> 
> The CC list was fine.  If you send Yuvraj and Bryant can figure out how to
> handle emails.  If we really decide that everyone should use
> --nogit-fallback then that should be made the default.

Understood. I suggested this flag because it helps me avoid sendig
patches to people who haven't explicity requested them. But you're
right, the decision is up to the sender.


Thanks,
Nikolay

      reply	other threads:[~2026-05-11 12:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10 11:02 [PATCH] staging: rtl8723bs: Fix coding style in ieee80211.h Pramod Maurya
2026-05-10 16:44 ` Nikolay Kulikov
     [not found]   ` <CAKR_b74W78QpNKvF_bU1EfT0WhXq4GxQDJiQ05Z454eABRsYWA@mail.gmail.com>
2026-05-10 18:04     ` Nikolay Kulikov
2026-05-11  8:51       ` Dan Carpenter
2026-05-11 12:55         ` Nikolay Kulikov [this message]

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=agHRvlftXepSzPDJ@archlinux \
    --to=nikolayof23@gmail.com \
    --cc=bryant.boatright@proton.me \
    --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=pramod.nexgen@gmail.com \
    --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