public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Charalampos Mitrodimas <charmitro@posteo.net>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
	linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: [PATCH 1/8] staging: sm750fb: Rename sii164GetDeviceID to sii164_get_device_id
Date: Thu, 23 Nov 2023 12:49:16 +0000	[thread overview]
Message-ID: <2023112355-upheld-prowess-9cf0@gregkh> (raw)
In-Reply-To: <20231113150512.1210869-2-charmitro@posteo.net>

On Mon, Nov 13, 2023 at 03:05:06PM +0000, Charalampos Mitrodimas wrote:
> Signed-off-by: Charalampos Mitrodimas <charmitro@posteo.net>
> ---
>  drivers/staging/sm750fb/ddk750_dvi.c    | 2 +-
>  drivers/staging/sm750fb/ddk750_sii164.c | 6 +++---
>  drivers/staging/sm750fb/ddk750_sii164.h | 2 +-
>  3 files changed, 5 insertions(+), 5 deletions(-)
> 

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/process/submitting-patches.rst for what is needed in
  order to properly describe the change.


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

  reply	other threads:[~2023-11-23 12:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 15:05 [PATCH 0/8] staging: sm750fb: Multiple camel cases renames Charalampos Mitrodimas
2023-11-13 15:05 ` [PATCH 1/8] staging: sm750fb: Rename sii164GetDeviceID to sii164_get_device_id Charalampos Mitrodimas
2023-11-23 12:49   ` Greg KH [this message]
2023-11-13 15:05 ` [PATCH 2/8] staging: sm750fb: Rename sii164ResetChip to sii164_reset_chip Charalampos Mitrodimas
2023-11-13 15:05 ` [PATCH 3/8] staging: sm750fb: Rename sii164GetChipString to sii164_get_chip_string Charalampos Mitrodimas
2023-11-13 15:05 ` [PATCH 4/8] staging: sm750fb: Rename sii164SetPower to sii164_set_power Charalampos Mitrodimas
2023-11-13 15:05 ` [PATCH 5/8] staging: sm750fb: Rename sii164EnableHotPlugDetection to sii164_enable_hot_plug_detection Charalampos Mitrodimas
2023-11-13 15:05 ` [PATCH 6/8] staging: sm750fb: Rename sii164IsConnected to sii164_is_connected Charalampos Mitrodimas
2023-11-13 15:05 ` [PATCH 7/8] staging: sm750fb: Rename sii164CheckInterrupt to sii164_check_interrupt Charalampos Mitrodimas
2023-11-13 15:05 ` [PATCH 8/8] staging: sm750fb: Rename sii164ClearInterrupt to sii164_clear_interrupt Charalampos Mitrodimas

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=2023112355-upheld-prowess-9cf0@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=charmitro@posteo.net \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=teddy.wang@siliconmotion.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