| Age | Commit message (Collapse) | Author |
|---|
|
For some reason, sometimes when the git logs contain non-ascii
characters, we get some conversion errors. This only happens if one
of the strings we use is explicitly unicode, otherwise everything is
fine. The only string we use that is of unicode type is the tree
names that comes from the configuration sections. To avoid issues,
convert the strings we get from the config file into ascii before
using it.
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Blue on black is really hard to read, use white on black.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Since CRYPTO_CMAC was introduced in 3.10, and mac80211
depends on it, we basically get nothing out of it anyway.
I'm not removing the support code (yet) since it actually
compiles, and perhaps somebody has a need for (certain)
kernel versions lower than 3.10.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
There's already a variable for the URL, use it.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
This reverts commit 3756f63528b044d6487bac046ad2972bc21583a5
and commit 709e720caa66816f32c6adc6050549fa40b9cf52 since
using built-in concurrency caused problems with --cocci-grep,
and not using that makes things slower.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
--yes allows skipping the question
--no-keep allows removing all installed data and reinstalling
--force does both (as before)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
My previous commit to optionally add a Change-Id missed two out
of three types of commits internally created by the tracker, add
the Change-Id to them as well.
Fixes: 7d89b544a1d9 ("git-tracker: add an option to add a Change-Id to commits")
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
This really breaks more than it fixes, afterwards it's no longer
possible to compile against those headers (modpost doesn't exist
due to the PIC issue.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
That way, the user at least has some feedback that something
is happening. Also add the missing try/finally so that the
temporary directory is cleaned up.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
When the resulting output trees are used with gerrit, it can be
useful for patches to have a Change-Id. Add an option to let the
script generate them.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Remove the leading . in the file, which has tripped up people
a few times already because it's hidden, and not always copied.
Change-Id: I48729af712f01b56cf43c4982321b989e33259f3
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
This allows using a different HTTP[S] proxy for input and output
trees, if necessary.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
This converts the backports-update-manager to use python3 instead of
python2. python3 is needed because new Debian packages are compressed
with the xz algorithm and only the tar module of python3 supports this
algorithm.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
It seems new versions of python make the os walk recurse more
than we used to before, our ckmake implementation was picking up
more kernels targets than obviously we want to build then. Fix
this by replacing the os.walk() with a simple os.listdir()
which just keeps us at the top level directory of lib/modules.
While at it, this adds the --develdebug option which lets you
debug the the directory naming it will use for display and what
directories it will traverse without actually compiling anything
and without using ncurses. For instance to debug or ckmake without
compilation you can use:
$ ckmake --allyesconfig --develdebug
Paths for kernels:
3.4.103-0304103-generic
3.9.11-030911-generic
3.2.62-030262-generic
3.16.2-031602-generic
3.11.10-031110-generic
3.8.13-030813-generic
3.5.7-03050712-generic
3.0.101-0300101-generic
3.15.10-031510-generic
3.6.11-030611-generic
3.13.11-031311-generic
3.1.10-030110-generic
3.10.54-031054-generic
3.3.8-030308-generic
3.7.10-030710-generic
3.14.18-031418-generic
3.17.0-031700rc3-generic
3.12.27-031227-generic
IDX VERSION DIRECTORY
1 3.0.101 /home/mcgrof/ksrc-backports/lib/modules/3.0.101-0300101-generic
2 3.1.10 /home/mcgrof/ksrc-backports/lib/modules/3.1.10-030110-generic
3 3.2.62 /home/mcgrof/ksrc-backports/lib/modules/3.2.62-030262-generic
4 3.3.8 /home/mcgrof/ksrc-backports/lib/modules/3.3.8-030308-generic
5 3.4.103 /home/mcgrof/ksrc-backports/lib/modules/3.4.103-0304103-generic
6 3.5.7 /home/mcgrof/ksrc-backports/lib/modules/3.5.7-03050712-generic
7 3.6.11 /home/mcgrof/ksrc-backports/lib/modules/3.6.11-030611-generic
8 3.7.10 /home/mcgrof/ksrc-backports/lib/modules/3.7.10-030710-generic
9 3.8.13 /home/mcgrof/ksrc-backports/lib/modules/3.8.13-030813-generic
10 3.9.11 /home/mcgrof/ksrc-backports/lib/modules/3.9.11-030911-generic
11 3.10.54 /home/mcgrof/ksrc-backports/lib/modules/3.10.54-031054-generic
12 3.11.10 /home/mcgrof/ksrc-backports/lib/modules/3.11.10-031110-generic
13 3.12.27 /home/mcgrof/ksrc-backports/lib/modules/3.12.27-031227-generic
14 3.13.11 /home/mcgrof/ksrc-backports/lib/modules/3.13.11-031311-generic
15 3.14.18 /home/mcgrof/ksrc-backports/lib/modules/3.14.18-031418-generic
16 3.15.10 /home/mcgrof/ksrc-backports/lib/modules/3.15.10-031510-generic
17 3.16.2 /home/mcgrof/ksrc-backports/lib/modules/3.16.2-031602-generic
18 3.17-rc3 /home/mcgrof/ksrc-backports/lib/modules/3.17.0-031700rc3-generic
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
pycocci is now part of Coccinelle upstream. Coccinelle has a plan
to actually extend multithreaded support to enable us to not have
to script this out. Until then pyccoci is used and I'll sync both
solutions up as there is a bit of latency between a coccinelle release
and what we may need from pycocci.
Please send patches or report issues about pycocci to the coccinelle
mailing list.
This commit syncs pycocci with the upstream pycocci with just one
minor change introduced:
commit cf8ef1aee7d40cddfee0f8707b2f481eb8258b4d
Author: Luis R. Rodriguez <mcgrof@suse.com>
Date: Fri May 29 15:15:57 2015 -0700
pycocci: update Python script to print errors clearly
When you run into errors with the pycocci script errors
seem cryptic, fix this. While at it also spit out what the
script will run, as typically when debugging you just want
to runt he same commands on your own.
For instance, when run on a 32 core machine you'll now see:
mcgrof@drvbp1 ~/linux-next (git::master)$ time pycocci rename-dma.cocci ./
spatch --sp-file rename-dma.cocci --in-place --recursive-includes --relax-include-path --use-coccigrep --timeout 120 --dir ./ -max 32 -index 0
...
spatch --sp-file rename-dma.cocci --in-place --recursive-includes --relax-include-path --use-coccigrep --timeout 120 --dir ./ -max 32 -index 27
real 0m50.074s
user 14m50.168s
sys 2m8.260s
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
The messages are only printed if something fails anyway, so
better ask for verbose messages to be able to better identify
what failed.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Various small things broken in the integration patchset, fix
them to actually make backports useful again.
For example, a driver using devcoredump wouldn't have worked
without these changes as it would depend on devcoredump, and
that wasn't backported due to the bugs, despite being in the
backport Kconfig file.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This enables support for using the backports project
to integrate device drivers from a future version of Linux
into an older version of Linux. What you end up seeing is
a backports submenu when configuring your kernel and the
ability to select specific device drivers from subsystems
supported through the Linux backports project.
At this time enabling one device driver from a future version
of Linux will require using only the latest version of the
subsystem modules and other subsystem drivers. For example
enabling cfg80211 and mac80211 from a future version of Linux
will require you to only use future version of the respective
device drivers. In order to enable the backported version of
802.11 drivers for example, you will have to enable first:
Networking support -->
Wireless -->
But under that menu disable all options, then jump to the backports
submenu to now enable:
Backports -->
cfg80211
mac80211
Wireless LAN --->
etc
You build these device drivers modular or built-in to the kernel.
Integration support requires only slight modifications to the original
kernel sources, one to the top level Kconfig to add our entry, and also
the top level Makefile to enable backports code to be part of the
built-in vmlinux.
Support for integration takes advantage over the existing infrastructure
added by Johannes to keep track of each indvidual change done by the
backports infrastructure if --gitdebug is used.
mcgrof@drvbp1 ~/backports (git::master)$ time ./gentree.py --clean \
/home/mcgrof/linux-next /home/mcgrof/build/backports-20141023
Copy original source files ...
Applying patches from patches to /home/mcgrof/build/backports-20141023
...
Modify Kconfig tree ...
Rewrite Makefiles and Kconfig files ...
Done!
real 1m27.942s
user 13m23.752s
sys 0m47.608s
1 3.0.101 [ OK ]
2 3.1.10 [ OK ]
3 3.2.62 [ OK ]
4 3.3.8 [ OK ]
5 3.4.104 [ OK ]
6 3.5.7 [ OK ]
7 3.6.11 [ OK ]
8 3.7.10 [ OK ]
9 3.8.13 [ OK ]
10 3.9.11 [ OK ]
11 3.10.58 [ OK ]
12 3.11.10 [ OK ]
13 3.12.31 [ OK ]
14 3.13.11 [ OK ]
15 3.14.22 [ OK ]
16 3.15.10 [ OK ]
17 3.16.6 [ OK ]
18 3.17.1 [ OK ]
19 3.18-rc1 [ OK ]
real 42m44.838s
user 1190m5.092s
sys 140m37.208s
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
|
|
The CPTCFG_ prefix already implies backport, when integration
is used we'd end up with a double BACKPORT_ prefix, so just
remove the existing one as its not needed.
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
|
|
The way we backport when packaging is to minimize the amount of
changes required by taking advantage of the fact that Kconfig
can treat CONFIG_ as an environment variable with getenv()
when parsing menu entries. When doing integration we don't want
to do this so instead we'll rely on the CONFIG_BACKPORT prefix.
This requires a bit of work on our current parsers, so to do that
identify the backport and provide that to helpers.
This also provides initial basic support for integration where no
additional code was required other than prefixes or ensuring certain
things are not done for integration. Before we expose integration
support we'll need to add quite a bit more things so this just assumes
integration is never desired.
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
This updates the kernel versions to test against to the most recent
versions.
Do not use 3.15.9, but 3.15.7 because there are some problems with the
define UTS_UBUNTU_RELEASE_ABI in the more recent kernel version, see:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1347879
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
This adds kernel 3.16 and updates some other kernel versions.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
This updates the kernel versions to test against to the most recent
versions.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
When the input tree had changes but the output doesn't get
any changes at all, then the shortlog was being generated
over all commits since no files were specified.
Catch this special case and instead of generating a shortlog
just add a note that no commits changed generated code.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
In spatch a ExecutionError was raised, but that causes the thread
to finish without closing the outfile and more importantly without
putting (ret, fn) tuple on the return queue. This results in the
threaded_spatch routine to get stuck on the ret_q.get() call. This
patch removes raising the ExecutionError and just return the tuple.
The non-zero return code will result in ExecutionErrorThread exception
anyway.
Signed-off-by: Arend van Spriel <arend@broadcom.com>
[mcgrof]: rebased to fit into pycocci
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
|
|
Older shutil.move does not seem to like it when there are
symlinks on a target, to account for this and to make things
clearer just split up the work on the lib/modules and usr/src
directory.
This fixes running devel/backports-update-manager on OpenSUSE 13.1
base install.
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
|
|
This converts rel-html.py to conform to the PEP 8 style
guide using autopep8. If using vi, consider adding this to
your .vimrc:
filetype indent plugin on
au FileType python setlocal tabstop=8 expandtab shiftwidth=4 softtabstop=4
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
|
