From: Jiri Slaby <jslaby@suse.cz>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@linux-foundation.org, werner@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: move proc_console.c to fs/proc/consoles.c
Date: Mon, 10 Jan 2011 20:21:51 +0100 [thread overview]
Message-ID: <4D2B5C4F.1090701@suse.cz> (raw)
In-Reply-To: <20110108173526.GA21042@p183.telecom.by>
On 01/08/2011 06:35 PM, Alexey Dobriyan wrote:
> Filename is supposed to match procfile name for random junk.
>
> Add __init while I'm at it.
>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> ---
>
> fs/proc/Makefile | 2
> fs/proc/consoles.c | 114 +++++++++++++++++++++++++++++++++++++++++++++++++
> fs/proc/proc_console.c | 114 -------------------------------------------------
> 3 files changed, 115 insertions(+), 115 deletions(-)
ACK.
thanks,
--
js
suse labs
prev parent reply other threads:[~2011-01-10 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 17:35 [PATCH] proc: move proc_console.c to fs/proc/consoles.c Alexey Dobriyan
2011-01-10 19:21 ` Jiri Slaby [this message]
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=4D2B5C4F.1090701@suse.cz \
--to=jslaby@suse.cz \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=werner@suse.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