From: chambilkethakur@gmail.com (Anuz Pratap Singh Tomar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Submitting patches to non-staging
Date: Fri, 4 Mar 2016 09:50:44 +0000 [thread overview]
Message-ID: <CAJnfX5vgmiu1SwgT_mscLAmVd=617Mj9tgx5JuGVdv0drkY1gQ@mail.gmail.com> (raw)
In-Reply-To: <CAAnMKKbXAKUDHXx7Mf-npnM1BRWVbNoA=BcZFB-xu5r6Ay46dA@mail.gmail.com>
On Thu, Mar 3, 2016 at 1:50 AM, Pratyush Patel <pratyushpatel.1995@gmail.com
> wrote:
> On Thu, Mar 3, 2016 at 1:15 AM, Christoph Lameter <cl@linux.com> wrote:
> > On Tue, 1 Mar 2016, Pratyush Patel wrote:
> >
> >> 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?
> >
> > Dont worry about staging. There is no staing for interrupts and timers.
> Go
> > direct and post to the relevant maintainers and lkml
> >
> >> I very much look forward to contributing my first patch!
> >
> > love to see it.
> >
>
> Here's the archive link:
> http://comments.gmane.org/gmane.linux.kernel/2165466
>
> Please do let me know in case I did something wrongly.
>
> Awaiting for it to be accepted!
>
> Single line changes like that can be sent to Janitors mailing list.
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
Thank you
Warm Regards
Anuz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160304/87215efc/attachment.html
next prev parent reply other threads:[~2016-03-04 9:50 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
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 [this message]
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='CAJnfX5vgmiu1SwgT_mscLAmVd=617Mj9tgx5JuGVdv0drkY1gQ@mail.gmail.com' \
--to=chambilkethakur@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).