All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qianqiang Liu <qianqiang.liu@163.com>
To: greg@kroah.com
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: How to contribute to the linux kernel
Date: Sun, 1 Sep 2024 08:35:16 +0800	[thread overview]
Message-ID: <ZtO2xFakr0VXrYLO@thinkpad.> (raw)
In-Reply-To: <2024083106-dubbed-sloppily-0aed@gregkh>

Hi Greg,

Thanks a lot.

Best,
Qianqiang Liu

On Sat, Aug 31, 2024 at 07:32:04PM +0200, Greg KH wrote:
> On Sat, Aug 31, 2024 at 04:17:35PM +0800, Qianqiang Liu wrote:
> > 
> > Hi all,
> > 
> > I am an embedded software engineer. I use Linux every day, and I appreciate its neatness and simplicity.
> > 
> > One day, I watched a video from Greg: https://youtu.be/LLBrBBImJt4, and I started wondering if maybe I could contribute to the Linux kernel. So, I sent a very simple (and maybe stupid) patch to the community:
> > 
> > > On Fri, Aug 30, 2024 at 04:54:38PM +0800, Qianqiang Liu wrote:
> > > There is no need to add parentheses around 'devcode != 0x0000' and
> > > 'devcode != 0x9320'
> > > 
> > > Signed-off-by: Qianqiang Liu <qianqiang.liu@163.com>
> > > ---
> > > drivers/staging/fbtft/fb_ili9320.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/staging/fbtft/fb_ili9320.c b/drivers/staging/fbtft/fb_ili9320.c
> > > index 0be7c2d51548..409b54cc562e 100644
> > > --- a/drivers/staging/fbtft/fb_ili9320.c
> > > +++ b/drivers/staging/fbtft/fb_ili9320.c
> > > @@ -37,7 +37,7 @@ static int init_display(struct fbtft_par *par)
> > >    devcode = read_devicecode(par);
> > >    fbtft_par_dbg(DEBUG_INIT_DISPLAY, par, "Device code: 0x%04X\n",
> > >              devcode);
> > > -    if ((devcode != 0x0000) && (devcode != 0x9320))
> > > +    if (devcode != 0x0000 && devcode != 0x9320)
> > >        dev_warn(par->info->device,
> > >             "Unrecognized Device code: 0x%04X (expected 0x9320)\n",
> > >            devcode);
> > > -- 
> > > 2.39.2
> > 
> > 
> > It turns out that the patch was rejected.
> 
> That's just because it's something that I don't think should be changed,
> not because it was "stupid" or anything like that.  It's been discussed
> many times in the past, not a big deal.
> 
> > So, my question is: how can I start contributing to the Linux kernel?
> > Maybe I could start by fixing some small bugs?
> 
> Sure, try reading this:
> 	https://lists.kernelnewbies.org/pipermail/kernelnewbies/2017-April/017765.html
> 
> Good luck!
> 
> greg k-h
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2024-09-01  0:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31  8:17 How to contribute to the linux kernel Qianqiang Liu
2024-08-31 17:32 ` Greg KH
2024-09-01  0:35   ` Qianqiang Liu [this message]
2024-09-02 17:49 ` Philipp Hortmann
2024-09-03  1:33   ` Qianqiang Liu
2024-09-03  2:11 ` Gustavo A. R. Silva
2024-09-03  2:50   ` Qianqiang Liu
2024-09-24  2:14   ` Qianqiang Liu
2024-09-24  5:13     ` Malatesh
2024-09-24  5:32       ` Qianqiang Liu
2024-09-24  7:20     ` Gustavo A. R. Silva

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=ZtO2xFakr0VXrYLO@thinkpad. \
    --to=qianqiang.liu@163.com \
    --cc=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    /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.