All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bharath Vedartham <linux.bhar@gmail.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] badblocks: Prefer unsigned int over unsigned
Date: Mon, 25 Feb 2019 22:33:22 +0530	[thread overview]
Message-ID: <20190225170322.GA10453@bharath12345-Inspiron-5559> (raw)
In-Reply-To: <CAFLxGvy1fKXEwZJwhD=aCbQ67HO+eK8T27KEfMrLu13ABvO1Wg@mail.gmail.com>

On Sun, Feb 24, 2019 at 04:50:51PM +0100, Richard Weinberger wrote:
> On Sun, Feb 24, 2019 at 4:38 PM Bharath Vedartham <linux.bhar@gmail.com> wrote:
> > I understand. I am starting out kernel hacking. I have been working on
> > fixing checkpatch.pl warnings. If you have any tasks for me in the
> > kernel, it would be great.
> >
> > I have also noticed a lot of warnings to replace printk with subsystem
> > specific warning functions. Is that a valuable change?
> 
> This is a very good start:
> https://lists.kernelnewbies.org/pipermail/kernelnewbies/2017-April/017765.html
> 
> Happy hacking and welcome! :-)
> 
> -- 
> Thanks,
> //richard

Hey! Thanks for the link Richard! I have read it and clearly understood
the message. I will work on understanding the kernel and writing my own
code for my own personal learning before jumping into tasks! Thanks for
your time!

Bharath

      reply	other threads:[~2019-02-25 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24 14:19 [PATCH] badblocks: Prefer unsigned int over unsigned Bharath Vedartham
2019-02-24 15:15 ` Jens Axboe
2019-02-24 15:37   ` Bharath Vedartham
2019-02-24 15:50     ` Richard Weinberger
2019-02-25 17:03       ` Bharath Vedartham [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=20190225170322.GA10453@bharath12345-Inspiron-5559 \
    --to=linux.bhar@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@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 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.