public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Niklas Söderlund" <niklas.soderlund@corigine.com>,
	"Dwaipayan Ray" <dwaipayanray1@gmail.com>,
	"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
	"Joe Perches" <joe@perches.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Andy Whitcroft" <apw@canonical.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oss-drivers@corigine.com,
	Simon Horman <simon.horman@corigine.com>,
	Louis Peens <louis.peens@corigine.com>
Subject: Re: [PATCH] checkpatch: warn for non-standard fixes tag style
Date: Tue, 30 Aug 2022 10:37:08 +0700	[thread overview]
Message-ID: <e79ebc62-7e44-3ec8-fdaf-42572c8ac75c@gmail.com> (raw)
In-Reply-To: <20220829155358.2546732-1-niklas.soderlund@corigine.com>

On 8/29/22 22:53, Niklas Söderlund wrote:
> +  **BAD_FIXES_TAG**
> +    The fixes line does not fall in line with the standards specified by the
> +    community.
> +
> +    See: https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes
> +
>  

Did you mean "The Fixes: tag is malformed"?

Also, mention that this message can occur when the tag is split
into multiple lines (e.g., when pasted in email program with word
wrapping enabled).

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

      parent reply	other threads:[~2022-08-30  3:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 15:53 [PATCH] checkpatch: warn for non-standard fixes tag style Niklas Söderlund
2022-08-30  3:06 ` Joe Perches
2022-09-05 10:49   ` Niklas Söderlund
2022-09-05 18:00     ` Joe Perches
2022-09-06  9:19       ` Niklas Söderlund
2022-08-30  3:37 ` Bagas Sanjaya [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=e79ebc62-7e44-3ec8-fdaf-42572c8ac75c@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=apw@canonical.com \
    --cc=corbet@lwn.net \
    --cc=dwaipayanray1@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=louis.peens@corigine.com \
    --cc=lukas.bulwahn@gmail.com \
    --cc=niklas.soderlund@corigine.com \
    --cc=oss-drivers@corigine.com \
    --cc=simon.horman@corigine.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox