mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Piro Yang <piroyangg@gmail.com>, gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: vme_user: Fixed prink formatting issue
Date: Sun, 17 Sep 2023 21:47:05 +0200	[thread overview]
Message-ID: <9548bc1c-23c9-427f-446e-61f051f14f9c@gmail.com> (raw)
In-Reply-To: <20230917192359.78711-1-piroyangg@gmail.com>

On 9/17/23 21:23, Piro Yang wrote:
> Fixed issue relating to prink message:
> 	*using __func__ to replace function's name
> 
> Issue found by checkpatch
> 
> Signed-off-by: Piro Yang<piroyangg@gmail.com>
> ---
>   drivers/staging/vme_user/vme.c | 14 +++++++-------
>   1 file changed, 7 insertions(+), 7 deletions(-)

Hi,

you need in any case a changelog what you changed with the v2 Version.

Your subject is to general. Please consider that the maintainer needs to 
recognize what it is about. So make it more unique.

Bye Philipp

  parent reply	other threads:[~2023-09-17 19:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 17:18 [PATCH] staging: vme_user: Fixed prink formatting issues Piro Yang
2023-09-17 18:11 ` [RESEND PATCH] " Piro Yang
2023-09-17 18:33   ` Greg KH
2023-09-17 18:34 ` [PATCH] " Greg KH
2023-09-17 19:23   ` [PATCH v2] staging: vme_user: Fixed prink formatting issue Piro Yang
2023-09-17 19:32     ` Greg KH
2023-09-17 19:47     ` Philipp Hortmann [this message]
2023-09-17 20:30       ` [PATCH v2] staging: vme_user: using __func__ to replace function's name in printk Piro Yang
2023-09-26  9:10         ` Greg KH

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=9548bc1c-23c9-427f-446e-61f051f14f9c@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=piroyangg@gmail.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

all inboxes | Powered by JetHome®