Thread (9 messages) 9 messages, 5 authors, 2016-05-10

Submitting patches to non-staging

From: Pratyush Patel <hidden>
Date: 2016-03-04 16:07:52

On Fri, Mar 4, 2016 at 3:20 PM, Anuz Pratap Singh Tomar
[off-list ref] wrote:

On Thu, Mar 3, 2016 at 1:50 AM, Pratyush Patel
[off-list ref] wrote:
quoted
On Thu, Mar 3, 2016 at 1:15 AM, Christoph Lameter [off-list ref] wrote:
quoted
On Tue, 1 Mar 2016, Pratyush Patel wrote:
quoted
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
quoted
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.
Yes, I sent it to the maintainer (Thomas Gleixner), linux-kernel, and
the kernel-janitors mailing lists.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help