public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Luka Gejak <luka.gejak@linux.dev>
Cc: Aadarsh 7001 <aadarshmandal9354@gmail.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	straube.linux@gmail.com, dan.carpenter@linaro.org,
	Ethan Tidmore <ethantidmore06@gmail.com>
Subject: Re: [PATCH] staging: rtl8723bs: fixed the trailing whitespaces/commented code
Date: Thu, 19 Mar 2026 07:38:02 +0100	[thread overview]
Message-ID: <2026031949-jeeringly-gravity-458c@gregkh> (raw)
In-Reply-To: <D3463B51-C2C5-4A9E-A7CA-5A3627AB04F8@linux.dev>

On Wed, Mar 18, 2026 at 10:06:57PM +0100, Luka Gejak wrote:
> On March 18, 2026 7:17:44 PM GMT+01:00, Greg KH <gregkh@linuxfoundation.org> wrote:
> >On Wed, Mar 18, 2026 at 12:54:38PM -0500, Ethan Tidmore wrote:
> >> On Wed Mar 18, 2026 at 10:11 AM CDT, Greg KH wrote:
> >> > On Wed, Mar 18, 2026 at 08:36:21PM +0530, Aadarsh 7001 wrote:
> >> >> On Wed, Mar 18, 2026 at 5:09 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >> >> 
> >> >> > On Wed, Mar 18, 2026 at 07:59:28AM +0100, Luka Gejak wrote:
> >> >> > > Hi Aadarsh,
> >> >> > >
> >> >> > > Thanks for submitting this patch, and good luck with your GSoC
> >> >> > application!
> >> >> >
> >> >> > Wait, what?  Is GSoC doing staging patches for "entrance" into the
> >> >> > program?  If so, SOMEONE needs to tell me this, otherwise I will have to
> >> >> > treat all of these as an abuse of the community review process and just
> >> >> > flat out reject all staging patches until the GSoC application process
> >> >> > is over.
> >> >> >
> >> >> This isn't ok, you all know better than to do this.
> >> >> >
> >> >> > Who is in charge of the kernel GSoC project this year?
> >> >> >
> >> >> > greg k-h
> >> >> 
> >> >> Sorry for the confusion, that wasn't my intention to abuse the community
> >> >> > review process. This is my effort to learn and contribute to the kernel.
> >> >> > I'll be extra care ful on this. Thank you for clarification.
> >> >
> >> > If you are applying for GSoC, this is not your fault.  I want to know
> >> > who the mentors that asked you to send this patch, where is that
> >> > documented?
> >> >
> >> > thanks,
> >> >
> >> > greg k-h
> >> 
> >> It's on the actual page for it [1]:
> >> 
> >> Create a small patch that fixes a trivial issue in drivers/staging. 
> >> See points 1) and 2) below to learn the process. Only after this patch 
> >> is accepted by the community you can go and work on the next step.
> >> 
> >> Thanks,
> >> 
> >> ET
> >> 
> >> [1] https://github.com/LinuxFoundationGSoC/ProjectIdeas/wiki/GSoC-2026-Device-Tree-Bindings
> >
> >And it points to a video of mine from 16 years ago
> >
> >{sigh}
> >
> >It would have been nice for someone from that project to give me the
> >heads-up that we would be getting a huge increase in our review load :(
> 
> Hey Greg, 
> Due to an unfortunate situation of current GSoC and an increase in 
> review load, I am able to assist with patch reviews if you want.

I never turn down patch reviews, as long as they are correct :)

  reply	other threads:[~2026-03-19  6:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-18  2:10 [PATCH] staging: rtl8723bs: fixed the trailing whitespaces/commented code Aadarsh Mandal
2026-03-18  6:52 ` Luka Gejak
2026-03-18  9:26   ` [PATCH] [PATCH] staging: rtl8723bs: clean up coding style in sdio_halinit.c V2 Aadarsh Mandal
2026-03-18  9:45     ` Luka Gejak
2026-03-18  9:53       ` Dan Carpenter
2026-03-18 10:43     ` [PATCH v3] staging: rtl8723bs: remove dead code Aadarsh Mandal
2026-03-18 11:17       ` Dan Carpenter
2026-03-18 11:33         ` Dan Carpenter
2026-03-18 11:37       ` Greg KH
2026-03-18  6:59 ` [PATCH] staging: rtl8723bs: fixed the trailing whitespaces/commented code Luka Gejak
2026-03-18 10:11   ` Greg KH
     [not found]     ` <CANQQrNO0GzqhYLj7DauWAoO=tVCz=86YaSjWWjAf-ER+UKmK6Q@mail.gmail.com>
2026-03-18 15:11       ` Greg KH
2026-03-18 17:54         ` Ethan Tidmore
2026-03-18 18:17           ` Greg KH
2026-03-18 21:06             ` Luka Gejak
2026-03-19  6:38               ` Greg KH [this message]
2026-03-19 14:11   ` [PATCH v4] staging: rtl8723bs: removed dead code Aadarsh Mandal
2026-03-20 14:46     ` [PATCH v5] staging: rtl8723bs: cleaned up patch formatting Aadarsh Mandal
2026-03-20 15:12       ` Luka Gejak
2026-03-19 14:12   ` [PATCH v4] staging: rtl8723bs: removed dead code Aadarsh Mandal
2026-03-19 14:18   ` Aadarsh Mandal
2026-03-19 17:46     ` Luka Gejak
2026-03-19 18:25     ` Ethan Tidmore
2026-03-19 18:26       ` Ethan Tidmore
2026-03-22 11:48 ` [PATCH v6] staging: rtl8723bs: remove commented-out code Aadarsh Mandal
2026-03-22 22:01   ` Ethan Tidmore
2026-03-23  8:47     ` Dan Carpenter
2026-03-24  4:07 ` [PATCH v7] " Aadarsh Mandal
2026-03-24  5:31   ` Luka Gejak
2026-03-24  6:54   ` Dan Carpenter
2026-03-24  8:12     ` Luka Gejak
2026-03-24  8:53       ` Dan Carpenter
     [not found]       ` <CANQQrNMNRuFw29zhckRYJ37Xf0YDXqZg9jnHgXznvNL=VfS7kA@mail.gmail.com>
2026-03-25  5:37         ` Luka Gejak

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=2026031949-jeeringly-gravity-458c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=aadarshmandal9354@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=ethantidmore06@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=luka.gejak@linux.dev \
    --cc=straube.linux@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