kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: sudipm.mukherjee@gmail.com (Sudip Mukherjee)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Submitting patches to non-staging
Date: Tue, 1 Mar 2016 21:24:50 +0530	[thread overview]
Message-ID: <CADVatmMENdraiv4_UntXjzT0Liw1eCe0C-1Y=mMs7bZhBGriTA@mail.gmail.com> (raw)
In-Reply-To: <CAAnMKKaBqxiJmdZBRcRcb=J0BS54K4tZnJjgYR_bkw2RZsXDXw@mail.gmail.com>

On Tue, Mar 1, 2016 at 9:16 PM, Pratyush Patel
<pratyushpatel.1995@gmail.com> wrote:
> Hello all,
>
> I am new to Linux kernel development and am hoping to contribute to
> the Linux community. I recently read Robert Love's LKD book, and have
> gone through some of the documents and patch submitting guidelines on
> kernelnewbies.org.
>
> I will be pursuing my undergraduate thesis research in the field of
> real-time (operating) systems and as such, I expect to be closely
> involved with the timer and interrupt subsystems in Linux (as well as
> other areas, but to a lesser degree). I am also hoping to work with
> the hrtimer subsystem, and while going through the latest code
> (4.5-rc6) of the same, I found a very minor code-level change that
> could be incorporated (redundant #ifdef). Would such a change in a
> core kernel file be acceptable coming from a beginner? Or should I aim
> for the staging drivers first?

If it is valid change it will be accepted. But better to start with staging,
learn and experience the process of patch submission then go to your
preferred subsystem.

regards
sudip

  reply	other threads:[~2016-03-01 15:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 15:46 Submitting patches to non-staging Pratyush Patel
2016-03-01 15:54 ` Sudip Mukherjee [this message]
2016-03-01 17:43   ` Pratyush Patel
2016-03-02 19:45 ` Christoph Lameter
2016-03-03  1:50   ` Pratyush Patel
2016-03-04  9:50     ` Anuz Pratap Singh Tomar
2016-03-04 16:07       ` Pratyush Patel
2016-03-04 16:22         ` Pratyush Patel
2016-05-10 14:19           ` Nahim `Naam` El Atmani

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='CADVatmMENdraiv4_UntXjzT0Liw1eCe0C-1Y=mMs7bZhBGriTA@mail.gmail.com' \
    --to=sudipm.mukherjee@gmail.com \
    --cc=kernelnewbies@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).