From: Randy Dunlap <rdunlap@infradead.org>
To: Shailendra Verma <shailendra.capricorn@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ionut Alexa <ionut.m.alexa@gmail.com>,
Paul McQuade <paulmcquad@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel:acct - Fix typos in comment to file header.
Date: Thu, 28 May 2015 17:11:34 -0700 [thread overview]
Message-ID: <5567AEB6.1080203@infradead.org> (raw)
In-Reply-To: <1432357759-4302-1-git-send-email-shailendra.capricorn@gmail.com>
On 05/22/15 22:09, Shailendra Verma wrote:
> Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com>
> ---
> kernel/acct.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/acct.c b/kernel/acct.c
> index 74963d1..fa972fa 100644
> --- a/kernel/acct.c
> +++ b/kernel/acct.c
> @@ -24,8 +24,8 @@
> * Now we silently close acct_file on attempt to reopen. Cleaned sys_acct().
> * XTerms and EMACS are manifestations of pure evil. 21/10/98, AV.
> *
> - * Fixed a nasty interaction with with sys_umount(). If the accointing
> - * was suspeneded we failed to stop it on umount(). Messy.
> + * Fixed a nasty interaction with with sys_umount(). If the accounting
You can also drop one of the double "with with" words.
> + * was suspended we failed to stop it on umount(). Messy.
> * Another one: remount to readonly didn't stop accounting.
> * Question: what should we do if we have CAP_SYS_ADMIN but not
> * CAP_SYS_PACCT? Current code does the following: umount returns -EBUSY
>
--
~Randy
prev parent reply other threads:[~2015-05-29 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 5:09 Shailendra Verma
2015-05-29 0:11 ` Randy Dunlap [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=5567AEB6.1080203@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=ionut.m.alexa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmcquad@gmail.com \
--cc=shailendra.capricorn@gmail.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®