public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mairo P. Rufus" <akoudanilo@gmail.com>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: <devel@driverdev.osuosl.org>, <trivial@kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: wlan-ng: Fix comments typos
Date: Thu, 11 Feb 2021 17:55:18 +0100	[thread overview]
Message-ID: <C96UXUQZSWD6.1BZ2DYOVBDNYL@uncertain> (raw)
In-Reply-To: <YCQSKNYU7zhcKHHl@kroah.com>

> Hi,
>
> This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
> a patch that has triggered this response. He used to manually respond
> to these common problems, but in order to save his sanity (he kept
> writing the same thing over and over, yet to different people), I was
> created. Hopefully you will not take offence and will fix the problem
> in your patch and resubmit it so that it can be accepted into the Linux
> kernel tree.
>
> You are receiving this message because of the following common error(s)
> as indicated below:
>
> - You did not specify a description of why the patch is needed, or
> possibly, any description at all, in the email body. Please read the
> section entitled "The canonical patch format" in the kernel file,
> Documentation/SubmittingPatches for what is needed in order to
> properly describe the change.
>
> - You did not write a descriptive Subject: for the patch, allowing Greg,
> and everyone else, to know what this patch is all about. Please read
> the section entitled "The canonical patch format" in the kernel file,
> Documentation/SubmittingPatches for what a proper Subject: line should
> look like.
>
> If you wish to discuss this problem further, or you have questions about
> how to resolve this issue, please feel free to respond to this email and
> Greg will reply once he has dug out from the pending patches received
> from other developers.
>
> thanks,
>
> greg k-h's patch email bot

After double checking, I still can't figure out what I did wrong. I'm
sorry for abusing your time, but can you help me on this one?


  reply	other threads:[~2021-02-11 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 14:59 [PATCH] staging: wlan-ng: Fix comments typos Mairo Paul Rufus
2021-02-10 17:04 ` Greg KH
2021-02-11 16:55   ` Mairo P. Rufus [this message]
2021-02-11 17:28     ` Greg KH
2021-02-18 16:15 ` Dan Carpenter

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=C96UXUQZSWD6.1BZ2DYOVBDNYL@uncertain \
    --to=akoudanilo@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox