* How to propose a patch to the kernel mainline
@ 2017-01-26 1:32 Abel
2017-01-26 6:33 ` Alexander Kapshuk
0 siblings, 1 reply; 4+ messages in thread
From: Abel @ 2017-01-26 1:32 UTC (permalink / raw)
To: kernelnewbies
Hi!
First, I apologize as I guess this topic has been treated many times here.
I'm already coding for a patch intended to be merged with the kernel
mainline. It adds a small new feature, so it's not a little bug fix, but
still not so big deal.
I'll get it compiling and working before I submit the patch to the mailing
list, that's clear to me; but I'm sure there will be mistakes, stuff I
didn't think/know about, some styling issues and, maybe, a technical
discussion of how it should be done.
*What I want to ask it's what are the best steps I should walk through in
order to get this patch merged.*
I've already done some modifications of the Linux kernel for university
works, I've also contributed to other open source projects. But I've never
tried to contribute to code to the upstream kernel code before.
*Greetings,*
* Akronix.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170126/c8c1a9f7/attachment.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* How to propose a patch to the kernel mainline
2017-01-26 1:32 How to propose a patch to the kernel mainline Abel
@ 2017-01-26 6:33 ` Alexander Kapshuk
2017-01-26 6:35 ` Alexander Kapshuk
0 siblings, 1 reply; 4+ messages in thread
From: Alexander Kapshuk @ 2017-01-26 6:33 UTC (permalink / raw)
To: kernelnewbies
On Thu, Jan 26, 2017 at 3:32 AM, Abel <akronix5@gmail.com> wrote:
> Hi!
>
> First, I apologize as I guess this topic has been treated many times here.
>
> I'm already coding for a patch intended to be merged with the kernel
> mainline. It adds a small new feature, so it's not a little bug fix, but
> still not so big deal.
> I'll get it compiling and working before I submit the patch to the mailing
> list, that's clear to me; but I'm sure there will be mistakes, stuff I
> didn't think/know about, some styling issues and, maybe, a technical
> discussion of how it should be done.
>
> What I want to ask it's what are the best steps I should walk through in
> order to get this patch merged.
>
> I've already done some modifications of the Linux kernel for university
> works, I've also contributed to other open source projects. But I've never
> tried to contribute to code to the upstream kernel code before.
>
> Greetings,
>
> Akronix.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
Please see in-tree documentation for development process found here,
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/Documentation/development-process?id=refs/tags/v4.9.5.
It addresses all of your queries.
^ permalink raw reply [flat|nested] 4+ messages in thread
* How to propose a patch to the kernel mainline
2017-01-26 6:33 ` Alexander Kapshuk
@ 2017-01-26 6:35 ` Alexander Kapshuk
2017-01-27 0:16 ` Abel
0 siblings, 1 reply; 4+ messages in thread
From: Alexander Kapshuk @ 2017-01-26 6:35 UTC (permalink / raw)
To: kernelnewbies
On Thu, Jan 26, 2017 at 8:33 AM, Alexander Kapshuk
<alexander.kapshuk@gmail.com> wrote:
> On Thu, Jan 26, 2017 at 3:32 AM, Abel <akronix5@gmail.com> wrote:
>> Hi!
>>
>> First, I apologize as I guess this topic has been treated many times here.
>>
>> I'm already coding for a patch intended to be merged with the kernel
>> mainline. It adds a small new feature, so it's not a little bug fix, but
>> still not so big deal.
>> I'll get it compiling and working before I submit the patch to the mailing
>> list, that's clear to me; but I'm sure there will be mistakes, stuff I
>> didn't think/know about, some styling issues and, maybe, a technical
>> discussion of how it should be done.
>>
>> What I want to ask it's what are the best steps I should walk through in
>> order to get this patch merged.
>>
>> I've already done some modifications of the Linux kernel for university
>> works, I've also contributed to other open source projects. But I've never
>> tried to contribute to code to the upstream kernel code before.
>>
>> Greetings,
>>
>> Akronix.
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>
> Please see in-tree documentation for development process found here,
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/Documentation/development-process?id=refs/tags/v4.9.5.
> It addresses all of your queries.
Here are a few more resources to consider:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/plain/Documentation/SubmittingPatches?id=refs/tags/v4.9.5
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/plain/Documentation/SubmittingDrivers?id=refs/tags/v4.9.5
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/plain/Documentation/CodingStyle?id=refs/tags/v4.9.5
^ permalink raw reply [flat|nested] 4+ messages in thread
* How to propose a patch to the kernel mainline
2017-01-26 6:35 ` Alexander Kapshuk
@ 2017-01-27 0:16 ` Abel
0 siblings, 0 replies; 4+ messages in thread
From: Abel @ 2017-01-27 0:16 UTC (permalink / raw)
To: kernelnewbies
Wow that's quite a lot to read ?
Thank you Alexander, I'll take a look at those.
Saludos,
* Abel.*
On 26 January 2017 at 07:35, Alexander Kapshuk <alexander.kapshuk@gmail.com>
wrote:
> On Thu, Jan 26, 2017 at 8:33 AM, Alexander Kapshuk
> <alexander.kapshuk@gmail.com> wrote:
> > On Thu, Jan 26, 2017 at 3:32 AM, Abel <akronix5@gmail.com> wrote:
> >> Hi!
> >>
> >> First, I apologize as I guess this topic has been treated many times
> here.
> >>
> >> I'm already coding for a patch intended to be merged with the kernel
> >> mainline. It adds a small new feature, so it's not a little bug fix, but
> >> still not so big deal.
> >> I'll get it compiling and working before I submit the patch to the
> mailing
> >> list, that's clear to me; but I'm sure there will be mistakes, stuff I
> >> didn't think/know about, some styling issues and, maybe, a technical
> >> discussion of how it should be done.
> >>
> >> What I want to ask it's what are the best steps I should walk through in
> >> order to get this patch merged.
> >>
> >> I've already done some modifications of the Linux kernel for university
> >> works, I've also contributed to other open source projects. But I've
> never
> >> tried to contribute to code to the upstream kernel code before.
> >>
> >> Greetings,
> >>
> >> Akronix.
> >>
> >> _______________________________________________
> >> Kernelnewbies mailing list
> >> Kernelnewbies at kernelnewbies.org
> >> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >>
> >
> > Please see in-tree documentation for development process found here,
> > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
> stable.git/tree/Documentation/development-process?id=refs/tags/v4.9.5.
> > It addresses all of your queries.
>
> Here are a few more resources to consider:
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
> stable.git/plain/Documentation/SubmittingPatches?id=refs/tags/v4.9.5
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
> stable.git/plain/Documentation/SubmittingDrivers?id=refs/tags/v4.9.5
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
> stable.git/plain/Documentation/CodingStyle?id=refs/tags/v4.9.5
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170127/9963c17c/attachment.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-01-27 0:16 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-26 1:32 How to propose a patch to the kernel mainline Abel
2017-01-26 6:33 ` Alexander Kapshuk
2017-01-26 6:35 ` Alexander Kapshuk
2017-01-27 0:16 ` Abel
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.