From: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
To: <Dmitry.Dunaev@baikalelectronics.ru>, <linux-mips@linux-mips.org>,
<linux-kernel@vger.kernel.org>
Cc: <Constantine.Gurin@baikalelectronics.ru>,
<Alexey.Malahov@baikalelectronics.ru>
Subject: Re: New MIPS SoC code insertion request
Date: Thu, 14 Apr 2016 16:29:23 +0100 [thread overview]
Message-ID: <570FB753.3060001@imgtec.com> (raw)
In-Reply-To: <E6691421972ADD4588ABC5DDDF6E279B87347565@NRMAIL.baikal.int>
Hi Dmitry,
Thank-you very much for reaching out to the mailing list.
The Linux kernel follows a structure for patch submissions.
There’s a tutorial on github with a pdf and readmes.
https://github.com/gregkh/kernel-tutorial
Tutorial Videos on YouTube by GregKH are also very useful.
https://www.youtube.com/watch?v=LLBrBBImJt4
https://www.youtube.com/watch?v=XXix80GCvpo
These will give an overview of the entire process.
It would be nice if you could push your current working kernel
somewhere on a git server where we could see the patches
and then provide guidance accordingly.
If you don't have a public-facing git server. You could just
push the code to a repository on github and share the link.
Regards,
ZubairLK
On 14/04/16 15:43, Dmitry.Dunaev@baikalelectronics.ru wrote:
> Good day!
>
> I'm Dmitry Dunaev, software designer from Baikal Electronics - Russian semiconductor company (http://www.baikalelectronics.com/). Some time ago we are released our first MIPS processor based on P5600 core (https://www.linux-mips.org/wiki/Baikal).
>
> Now we have this SoC in silicon. Also we have released several revisions of development boards for our SoC. So it seems that we ready to add our platform code into Linux kernel mainline.
>
> Could you please clarify me what steps we should to do to add our code into kernel repositary?
>
> Best regards,
> Dmitry Dunaev
> http://www.baikalelectronics.com/
>
next prev parent reply other threads:[~2016-04-14 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E6691421972ADD4588ABC5DDDF6E279B8734754A@NRMAIL.baikal.int>
2016-04-14 14:43 ` New MIPS SoC code insertion request Dmitry.Dunaev
2016-04-14 15:29 ` Zubair Lutfullah Kakakhel [this message]
2016-04-14 17:36 ` Ralf Baechle
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=570FB753.3060001@imgtec.com \
--to=zubair.kakakhel@imgtec.com \
--cc=Alexey.Malahov@baikalelectronics.ru \
--cc=Constantine.Gurin@baikalelectronics.ru \
--cc=Dmitry.Dunaev@baikalelectronics.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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