diff options
| author | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2021-03-05 14:17:49 +0100 |
|---|---|---|
| committer | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2021-03-05 14:21:41 +0100 |
| commit | 814ba8d3ec6153a36bbdb54fedcdfcc720b3a789 (patch) | |
| tree | 71e7fb8d0afa387624ef45ecf2a8bce31e85aadd /AUTHORS | |
| parent | 83ef4ddb9592e796ac61481e5d0e7cf904509c67 (diff) | |
| download | external_usbip-kernel-samsung-smdk4412-814ba8d3ec6153a36bbdb54fedcdfcc720b3a789.tar.gz external_usbip-kernel-samsung-smdk4412-814ba8d3ec6153a36bbdb54fedcdfcc720b3a789.tar.bz2 external_usbip-kernel-samsung-smdk4412-814ba8d3ec6153a36bbdb54fedcdfcc720b3a789.zip | |
Move usbip tools to the top directory
We can't simply add an Android.mk inside the kernel sources,
otherwise we have a build error like this one:
build/core/base_rules.mk:157:
*** out/target/product/i9300/obj/KERNEL_OBJ/source/drivers/staging/usbip/userspace:
MODULE.TARGET.EXECUTABLES.usbip already defined by
kernel/samsung/smdk4412/drivers/staging/usbip/userspace. Stop.
This is because the Android.mk gets copied in
out/target/product/i9300/obj/KERNEL_OBJ/source/ along with the rest
of the kernel source code.
So instead we just re-imported all the commits which touch the
drivers/staging/usbip/userspace/ directory inside the smdk4412 kernel.
Since when doing that, the code ends up in its original location in
drivers/staging/usbip/userspace/, we need to move it to the top
directory.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Diffstat (limited to 'AUTHORS')
| -rw-r--r-- | AUTHORS | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -0,0 +1,2 @@ +Takahiro Hirofuchi +Robert Leibl |
