Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754742AbbBTQua (ORCPT ); Fri, 20 Feb 2015 11:50:30 -0500 Received: from thoth.sbs.de ([192.35.17.2]:46283 "EHLO thoth.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752301AbbBTQu3 (ORCPT ); Fri, 20 Feb 2015 11:50:29 -0500 Message-ID: <54E765D1.6060405@siemens.com> Date: Fri, 20 Feb 2015 17:50:25 +0100 From: Jan Kiszka User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: Andrew Morton , Linux Kernel Mailing List Subject: [PATCH] scripts/gdb: Add empty package initialization script Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1159 Lines: 32 This got lost during the initial merge process: Python requires an __init__.py script, even if empty, in order to accept a directory as package. Add it, this time as a none-empty file. Signed-off-by: Jan Kiszka --- Andrew, seems your import scripting drops empty files from patches. This happened with __init__.py in "scripts/gdb: add infrastructure". Or it was a side effect of v12 vs. v13 processing. Anyway, this is the fix. Which is the preferred route for future changes to files in scripts/gdb? Via your tree? scripts/gdb/linux/__init__.py | 1 + 1 file changed, 1 insertion(+) create mode 100644 scripts/gdb/linux/__init__.py diff --git a/scripts/gdb/linux/__init__.py b/scripts/gdb/linux/__init__.py new file mode 100644 index 0000000..4680fb1 --- /dev/null +++ b/scripts/gdb/linux/__init__.py @@ -0,0 +1 @@ +# nothing to do for the initialization of this package -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/