From: Greg KH <gregkh@linuxfoundation.org>
To: hamohammed.sa@gmail.com
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v3] Staging: lustre: Fix line over 80 characters
Date: Sun, 1 Mar 2015 16:51:24 -0800 [thread overview]
Message-ID: <20150302005124.GA29200@kroah.com> (raw)
In-Reply-To: <20150301144310.GA7807@example.com>
On Sun, Mar 01, 2015 at 05:43:10PM +0300, Haneen Mohammed wrote:
> This patch splits line over 80 characters addressing checkpatch.pl
> warning.
>
> Signed-off-by: Haneen Mohammed <hamohammed.sa@gmail.com>
> ---
> v3: fix identation.
> v2: edit subject line.
>
> drivers/staging/lustre/lustre/ldlm/ldlm_request.c | 44 ++++++++++++++---------
> 1 file changed, 27 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_request.c b/drivers/staging/lustre/lustre/ldlm/ldlm_request.c
> index 287da32..ec09c08 100644
> --- a/drivers/staging/lustre/lustre/ldlm/ldlm_request.c
> +++ b/drivers/staging/lustre/lustre/ldlm/ldlm_request.c
> @@ -98,13 +98,16 @@ int ldlm_expired_completion_wait(void *data)
> static unsigned long next_dump, last_dump;
>
> LCONSOLE_WARN("lock timed out (enqueued at "CFS_TIME_T", "
> - CFS_DURATION_T"s ago)\n",
> - lock->l_last_activity,
> - cfs_time_sub(get_seconds(),
> - lock->l_last_activity));
> - LDLM_DEBUG(lock, "lock timed out (enqueued at " CFS_TIME_T ", " CFS_DURATION_T "s ago); not entering recovery in server code, just going back to sleep",
> - lock->l_last_activity,
> - cfs_time_sub(get_seconds(),
> + CFS_DURATION_T"s ago)\n",
> + lock->l_last_activity,
> + cfs_time_sub(get_seconds(),
> + lock->l_last_activity));
> + LDLM_DEBUG(lock,
> + "lock timed out (enqueued at "
Very odd indentation :(
prev parent reply other threads:[~2015-03-02 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 14:43 [PATCH v3] Staging: lustre: Fix line over 80 characters Haneen Mohammed
2015-03-02 0:51 ` Greg KH [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=20150302005124.GA29200@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hamohammed.sa@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.