diff options
| author | Mcgrof <anonymous.contributor@example.org> | 2013-12-02 19:04:44 +0000 |
|---|---|---|
| committer | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2024-10-04 15:47:32 -0400 |
| commit | 22d4b4223ebe93ad359b042f332d6bab21de84a9 (patch) | |
| tree | 5d6118a8a070a161317a3034e0e43de16e3a964c | |
| parent | a859c5daf45445a5559a750e6bb0f7842e778218 (diff) | |
| download | backports-22d4b4223ebe93ad359b042f332d6bab21de84a9.tar.gz | |
Update Documentation/backports/hacking
| -rw-r--r-- | wiki/Documentation_backports_hacking.mediawiki | 17 |
1 files changed, 5 insertions, 12 deletions
diff --git a/wiki/Documentation_backports_hacking.mediawiki b/wiki/Documentation_backports_hacking.mediawiki index 38910c4..0749476 100644 --- a/wiki/Documentation_backports_hacking.mediawiki +++ b/wiki/Documentation_backports_hacking.mediawiki @@ -10,7 +10,7 @@ The project aims to optimize the backporting process by not only providing backp backports backports a few subsystems down to older kernels. To be able to synchronize backporting the latest and greatest the [https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git linux-next.git] tree is used as its main source for kernel updates. backports brings a general kernel compatibility part containing some backported c functions and header files in addition to patches for code in linux-next to make it work on older kernel versions and with the general kernel compatibility part. -This is now in one repository [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git backports.git] and not spitted over two any more. +This is now in one repository [https://git.kernel.org/cgit/linux/kernel/git/backports/backports.git backports.git] and not spitted over two any more. You can generate backports based on different trees depending on your needs. We are supporting build based on [https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/ linux-next.git], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ linux.git] and [https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/ linux-stable.git]. You can also generate builds based on your own tree, but then you probably have to patch backports yourself to add support for that. @@ -24,18 +24,11 @@ To generate a own backport release based on linux-next you need the following gi <code> <pre> -git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/backports.git +git://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git </pre> </code> -Currently the recent backports code is located in a different git repository, use this instead of other backports.git repository: -<code> -<pre> -https://github.com/hauke/backports.git -</pre> -</code> - As linux-next changes often you should start with a working version by using a tagged version from linux-next.git and backports.git with the same date in it like backports-20130607 and next-20130607. This is a combination where someone already tested that the patches are still applying. After you have checked out some version of these git trees, you can start generating a tar by running ./gentree.py in the backports tree. @@ -49,7 +42,7 @@ This will take the path to the already checked out linux-next kernel as the seco = Adding new driver = -This is a list of steps to be done when adding a new driver. Not all steps are needed for every new driver it depends on what type of driver is added. You can take the patch adding support for the ieee802154 subsystem as a reference [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/commit/?id=a42aa4d474e5859164a00bf451970fb58b676fcf]. +This is a list of steps to be done when adding a new driver. Not all steps are needed for every new driver it depends on what type of driver is added. You can take the patch adding support for the ieee802154 subsystem as a reference [https://git.kernel.org/cgit/linux/kernel/git/backports/backports.git/commit/?id=a42aa4d474e5859164a00bf451970fb58b676fcf]. You should target the master branch of the backports repository. @@ -68,11 +61,11 @@ Features being backported should either be backported into a respective backport = Backports Kconfig operation = -Go read the [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/tree/devel/doc/kconfig-operation backports kconfig operation] documentation. +Go read the [https://git.kernel.org/cgit/linux/kernel/git/backports/backports.git/tree/devel/doc/kconfig-operation backports kconfig operation] documentation. = Backports Makefile operation = -Go read the [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/tree/devel/doc/makefile-operation backports Makefile operation] documentation. +Go read the [https://git.kernel.org/cgit/linux/kernel/git/backports/backports.git/tree/devel/doc/makefile-operation backports Makefile operation] documentation. = Sending patches = |