From: Stefan Assmann <sassmann@kpanic.de>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>, backports@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, yann.morin.1998@free.fr,
mmarek@suse.cz, "Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: [RFC v2 4/4] backports: add kernl integration support to gentree.py
Date: Wed, 29 Oct 2014 16:36:59 +0100 [thread overview]
Message-ID: <5451099B.7090102@kpanic.de> (raw)
In-Reply-To: <1414570902-5675-5-git-send-email-mcgrof@do-not-panic.com>
On 29.10.2014 09:21, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@suse.com>
>
> Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
> ---
> backport/Kconfig | 54 --------
> backport/Kconfig.sources | 23 ++++
> backport/Makefile | 3 +-
> backport/Makefile.kernel | 18 +++
> backport/backport-include/backport/backport.h | 2 +
> backport/compat/Makefile | 4 +
> gentree.py | 186 +++++++++++++++++++++-----
> lib/bpversion.py | 48 +++++++
> lib/kconfig.py | 12 +-
> 9 files changed, 260 insertions(+), 90 deletions(-)
> delete mode 100644 backport/Kconfig
> create mode 100644 backport/Kconfig.sources
> create mode 100644 lib/bpversion.py
This breaks my usual gentree.py run.
~/backports> ./gentree.py --clean --git-revision next-20141023 ~/backports/linux-next/ /dev/shm/backports-next
Get original source files from git ...
Traceback (most recent call last):
File "./gentree.py", line 1028, in <module>
ret = _main()
File "./gentree.py", line 517, in _main
logwrite=logwrite)
File "./gentree.py", line 637, in process
copy_files(os.path.join(source_dir, 'backport'), backport_files, args.outdir)
File "./gentree.py", line 175, in copy_files
os.path.join(outdir, tgtitem))
File "/usr/lib64/python2.7/shutil.py", line 119, in copy
copyfile(src, dst)
File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile
with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory: '/root/backports/backport/Kconfig.package'
I don't see Kconfig.package in this series. Did you forget to git add it?
Stefan
next prev parent reply other threads:[~2014-10-29 15:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 8:21 [RFC v2 0/4] backports: kernel integration support Luis R. Rodriguez
2014-10-29 8:21 ` [RFC v2 1/4] backports: replace CPTCFG prefix for CONFIG_BACKPORT Luis R. Rodriguez
2014-10-31 7:41 ` Johannes Berg
2014-10-31 19:34 ` Luis R. Rodriguez
2014-10-31 20:22 ` Johannes Berg
2014-10-31 20:33 ` Luis R. Rodriguez
2014-11-03 19:30 ` Luis R. Rodriguez
2014-11-03 19:40 ` Johannes Berg
2014-11-03 19:56 ` Luis R. Rodriguez
2014-11-03 20:20 ` Johannes Berg
2014-11-03 20:21 ` Luis R. Rodriguez
2014-11-03 20:24 ` Johannes Berg
2014-11-03 20:26 ` Luis R. Rodriguez
2014-10-29 8:21 ` [RFC v2 2/4] backports: replace BACKPORT_PWD with BACKPORT_DIR Luis R. Rodriguez
2014-10-31 7:41 ` Johannes Berg
2014-10-31 19:35 ` Luis R. Rodriguez
2014-10-29 8:21 ` [RFC v2 3/4] backports: use BACKPORT_DIR prefix on kconfig sources Luis R. Rodriguez
2014-10-31 7:46 ` Johannes Berg
2014-10-31 20:03 ` Luis R. Rodriguez
2014-10-29 8:21 ` [RFC v2 4/4] backports: add kernl integration support to gentree.py Luis R. Rodriguez
2014-10-29 15:36 ` Stefan Assmann [this message]
2014-10-29 16:00 ` Luis R. Rodriguez
2014-10-31 7:50 ` Johannes Berg
2014-10-31 20:10 ` Luis R. Rodriguez
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=5451099B.7090102@kpanic.de \
--to=sassmann@kpanic.de \
--cc=backports@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mcgrof@suse.com \
--cc=mmarek@suse.cz \
--cc=yann.morin.1998@free.fr \
/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 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.