The patch titled
Arch: add gitignore file for relocs in arch i386 fix
has been added to the -mm tree. Its filename is
add-gitignore-file-for-relocs-in-arch-i386-fix.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: Arch: add gitignore file for relocs in arch i386 fix
From: Jiri Slaby <jirislaby@xxxxxxxxx>
add gitignore file for relocs in arch i386 fix
The .gitigonre was intended to be in arch/ subtree.
Signed-off-by: Jiri Slaby <jirislaby@xxxxxxxxx>
Cc: Thomas Meyer <thomas@xxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
arch/i386/boot/compressed/.gitignore | 1 +
i386/boot/compressed/.gitignore | 1 -
2 files changed, 1 insertion(+), 1 deletion(-)
diff -puN /dev/null arch/i386/boot/compressed/.gitignore
--- /dev/null
+++ a/arch/i386/boot/compressed/.gitignore
@@ -0,0 +1 @@
+relocs
diff -puN i386/boot/compressed/.gitignore~add-gitignore-file-for-relocs-in-arch-i386-fix /dev/null
--- a/i386/boot/compressed/.gitignore
+++ /dev/null
@@ -1 +0,0 @@
-relocs
_
Patches currently in -mm which might be from jirislaby@xxxxxxxxx are
add-gitignore-file-for-relocs-in-arch-i386-fix.patch
char-mxser-fix-oops-when-removing-opened.patch
char-isicom-eliminate-spinlock-recursion.patch
git-input.patch
char-tty-delete-wake_up_interruptible-after-tty_wakeup.patch
char-isicom-remove-tty_hangwakeup-bottomhalves.patch
mxser-remove-ambiguous-redefinition-of-init_work.patch
make-drivers-char-mxser_newcmxser_hangup-static.patch
char-isicom-fix-locking-in-isr.patch
char-isicom-augment-card_reset.patch
char-isicom-check-card-state-in-isr.patch
char-isicom-support-higher-rates.patch
char-isicom-correct-probing-removing.patch
char-tty_wakeup-cleanup.patch
char-mxser_new-mark-init-functions.patch
char-mxser_new-remove-useless-spinlock.patch
char-serial167-cleanup.patch
char-n_r3964-cleanup.patch
shrink_slab-handle-bad-shrinkers.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
