[PATCH] scripts/gdb: Add empty package initialization script

[Jan Kiszka]

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 <jan.kiszka@xxxxxxxxxxx>
---

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/