From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: akpm@linux-foundation.org, arnd@arndb.de, davej@redhat.com,
dhowells@redhat.com, mtk.manpages@gmail.com,
paulmck@linux.vnet.ibm.com, tglx@linutronix.de
Subject: + create-non-empty-arch-x86-include-uapi-asm-files.patch added to -mm tree
Date: Mon, 17 Dec 2012 14:17:15 -0800 [thread overview]
Message-ID: <20121217230748.6ADDB200057@hpza10.eem.corp.google.com> (raw)
The patch titled
Subject: create non-empty arch/x86/include/uapi/asm/ files
has been added to the -mm tree. Its filename is
create-non-empty-arch-x86-include-uapi-asm-files.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: create non-empty arch/x86/include/uapi/asm/ files
patch(1) doesn't create zero-length files, so my kernel didn't compile.
Put something in these files so patch(1) actually creates them.
Cc: David Howells <dhowells@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Dave Jones <davej@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/x86/include/uapi/asm/hw_breakpoint.h | 1 +
arch/x86/include/uapi/asm/setup.h | 1 +
2 files changed, 2 insertions(+)
diff -puN /dev/null arch/x86/include/uapi/asm/hw_breakpoint.h
--- /dev/null
+++ a/arch/x86/include/uapi/asm/hw_breakpoint.h
@@ -0,0 +1 @@
+/* */
diff -puN /dev/null arch/x86/include/uapi/asm/setup.h
--- /dev/null
+++ a/arch/x86/include/uapi/asm/setup.h
@@ -0,0 +1 @@
+/* */
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
origin.patch
lseek-the-whence-argument-is-called-whence.patch
drivers-video-backlight-lp855x_blc-use-generic-pwm-functions-fix.patch
backlight-add-of_find_backlight_by_node-function-fix.patch
backlight-88pm860x_bl-remove-an-unnecessary-line-continuation-fix.patch
binfmt_elf-fix-corner-case-kfree-of-uninitialized-data-checkpatch-fixes.patch
rtc-avoid-calling-platform_device_put-twice-in-test_init-fix.patch
procfs-add-vmflags-field-in-smaps-output-v4.patch
procfs-add-vmflags-field-in-smaps-output-v4-fix.patch
docs-add-documentation-about-proc-pid-fdinfo-fd-output-fix.patch
scatterlist-dont-bug-when-we-can-trivially-return-a-proper-error-fix.patch
create-non-empty-arch-x86-include-uapi-asm-files.patch
mm-memoryc-suppress-warning.patch
reply other threads:[~2012-12-17 23:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121217230748.6ADDB200057@hpza10.eem.corp.google.com \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=davej@redhat.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox