All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: kernel-janitors@vger.kernel.org, trivial@kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] Fix a few typos around the word "destroy"
Date: Tue, 25 Nov 2014 02:21:46 +0000	[thread overview]
Message-ID: <5473E7BA.5050703@infradead.org> (raw)
In-Reply-To: <54736422.90409@users.sourceforge.net>

On 11/24/2014 09:00 AM, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Mon, 24 Nov 2014 17:34:23 +0100
> Subject: [PATCH 0/6] Fix a few typos around the word "destroy"
>
> The word "destroy" was mistyped in some files.

For all 6 patches;
Acked-by: Randy Dunlap <rdunlap@infradead.org>

However, in th3 future, please document each patch as described in
Documentation/SubmittingPatches:

   Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
   instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy
   to do frotz", as if you are giving orders to the codebase to change
   its behaviour.

E.g., instead of:

A word was corrected in the description for a parameter of
the mmp_unregister_path() function.

Use:

Correct the description of a parameter of the mmp_unregister_path()
function.

Thanks.

>
> Markus Elfring (6):
>    isci: Fix a typo for the word "destroy"
>    SCSI-libfc: Fix typos for the word "destroy"
>    video: fbdev-MMP: Fix typos for the word "destroy"
>    f2fs: Fix typos for the word "destroy" in jump labels
>    video: fbdev-MMP: Fix a typo for the word "destroyed"
>    Documentation-SCSI: Fix a typo for the word "destroy"
>
>   Documentation/scsi/ChangeLog.lpfc | 2 +-
>   drivers/scsi/isci/remote_device.c | 2 +-
>   drivers/scsi/libfc/fc_fcp.c       | 4 ++--
>   drivers/video/fbdev/mmp/core.c    | 6 +++---
>   fs/f2fs/node.c                    | 8 ++++----
>   5 files changed, 11 insertions(+), 11 deletions(-)
>


-- 
~Randy

WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@infradead.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: kernel-janitors@vger.kernel.org, trivial@kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] Fix a few typos around the word "destroy"
Date: Mon, 24 Nov 2014 18:21:46 -0800	[thread overview]
Message-ID: <5473E7BA.5050703@infradead.org> (raw)
In-Reply-To: <54736422.90409@users.sourceforge.net>

On 11/24/2014 09:00 AM, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Mon, 24 Nov 2014 17:34:23 +0100
> Subject: [PATCH 0/6] Fix a few typos around the word "destroy"
>
> The word "destroy" was mistyped in some files.

For all 6 patches;
Acked-by: Randy Dunlap <rdunlap@infradead.org>

However, in th3 future, please document each patch as described in
Documentation/SubmittingPatches:

   Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
   instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy
   to do frotz", as if you are giving orders to the codebase to change
   its behaviour.

E.g., instead of:

A word was corrected in the description for a parameter of
the mmp_unregister_path() function.

Use:

Correct the description of a parameter of the mmp_unregister_path()
function.

Thanks.

>
> Markus Elfring (6):
>    isci: Fix a typo for the word "destroy"
>    SCSI-libfc: Fix typos for the word "destroy"
>    video: fbdev-MMP: Fix typos for the word "destroy"
>    f2fs: Fix typos for the word "destroy" in jump labels
>    video: fbdev-MMP: Fix a typo for the word "destroyed"
>    Documentation-SCSI: Fix a typo for the word "destroy"
>
>   Documentation/scsi/ChangeLog.lpfc | 2 +-
>   drivers/scsi/isci/remote_device.c | 2 +-
>   drivers/scsi/libfc/fc_fcp.c       | 4 ++--
>   drivers/video/fbdev/mmp/core.c    | 6 +++---
>   fs/f2fs/node.c                    | 8 ++++----
>   5 files changed, 11 insertions(+), 11 deletions(-)
>


-- 
~Randy

  parent reply	other threads:[~2014-11-25  2:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 17:00 [PATCH 0/6] Fix a few typos around the word "destroy" SF Markus Elfring
2014-11-24 17:00 ` SF Markus Elfring
2014-11-24 17:08 ` [PATCH 1/6] isci: Fix a typo for " SF Markus Elfring
2014-11-24 17:08   ` SF Markus Elfring
2014-11-24 17:15 ` [PATCH 2/6] SCSI-libfc: Fix typos " SF Markus Elfring
2014-11-24 17:15   ` SF Markus Elfring
2014-11-24 17:19 ` [PATCH 3/6] video: fbdev-MMP: " SF Markus Elfring
2014-11-24 17:19   ` SF Markus Elfring
2014-11-25 10:55   ` Tomi Valkeinen
2014-11-25 10:55     ` Tomi Valkeinen
2014-11-24 17:24 ` [PATCH 4/6] f2fs: Fix typos for the word "destroy" in jump labels SF Markus Elfring
2014-11-24 17:24   ` SF Markus Elfring
2014-11-24 21:42   ` Jaegeuk Kim
2014-11-24 21:42     ` Jaegeuk Kim
2014-11-24 17:28 ` [PATCH 5/6] video: fbdev-MMP: Fix a typo for the word "destroyed" SF Markus Elfring
2014-11-24 17:28   ` SF Markus Elfring
2014-11-24 17:31 ` [PATCH 6/6] Documentation-SCSI: Fix a typo for the word "destroy" SF Markus Elfring
2014-11-24 17:31   ` SF Markus Elfring
2014-11-25  2:21 ` Randy Dunlap [this message]
2014-11-25  2:21   ` [PATCH 0/6] Fix a few typos around " Randy Dunlap

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=5473E7BA.5050703@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=elfring@users.sourceforge.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.org \
    /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.