On Thu, Mar 3, 2016 at 10:07 PM, <kernelnewbies-request@kernelnewbies.org> wrote:
Send Kernelnewbies mailing list submissions to kernelnewbies@kernelnewbies.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies or, via email, send a message with subject or body 'help' to kernelnewbies-request@kernelnewbies.org
You can reach the person managing the list at kernelnewbies-owner@kernelnewbies.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of Kernelnewbies digest..."
Today's Topics:
1. Re: Submitting patches to non-staging (Christoph Lameter) 2. Re: Submitting patches to non-staging (Pratyush Patel) 3. Fw: new important message (bear.yogi@gmx.de) 4. Re: where is disk block access in kernel ? (Mulyadi Santosa) 5. Re: where is disk block access in kernel ? (Valdis.Kletnieks@vt.edu) 6. remote system call (Nitin Varyani) 7. Re: remote system call (Mulyadi Santosa)
----------------------------------------------------------------------
Message: 1 Date: Wed, 2 Mar 2016 13:45:54 -0600 (CST) From: Christoph Lameter <cl@linux.com> Subject: Re: Submitting patches to non-staging To: Pratyush Patel <pratyushpatel.1995@gmail.com> Cc: kernelnewbies@kernelnewbies.org Message-ID: <alpine.DEB.2.20.1603021344420.3497@east.gentwo.org> Content-Type: text/plain; charset=US-ASCII
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.
------------------------------
Message: 2 Date: Thu, 3 Mar 2016 07:20:18 +0530 From: Pratyush Patel <pratyushpatel.1995@gmail.com> Subject: Re: Submitting patches to non-staging To: Christoph Lameter <cl@linux.com> Cc: kernelnewbies <kernelnewbies@kernelnewbies.org> Message-ID: <CAAnMKKbXAKUDHXx7Mf-npnM1BRWVbNoA= BcZFB-xu5r6Ay46dA@mail.gmail.com> Content-Type: text/plain; charset=UTF-8
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!
It seems to be a valid change and should be accepted in the kernel.
You may probably change the commit message something like.. " removing nested macro definition (CONFIG_SMP)" if you want. good luck -- Vishwas
------------------------------
Message: 3 Date: Thu, 3 Mar 2016 05:37:11 +0300 From: <bear.yogi@gmx.de> Subject: Fw: new important message To: "kernelnewbies" <kernelnewbies@kernelnewbies.org>, "leo kirotawa" <kirotawa@gmail.com>, "lifelong0811" <lifelong0811@126.com>, "lind.lampe@gmx.de" <lind.lampe@gmx.de>, "linux-api" <linux-api@vger.kernel.org> Message-ID: <0000073edf2f$53e14ef2$6fb257ae$@gmx.de> Content-Type: text/plain; charset="us-ascii"
Hello!
New message, please read <http://majorinvesting.com/longer.php?drpr>
bear.yogi@gmx.de