All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Sam Muhammed <jane.pnx9@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v2 2/7] Staging: kpc2000: kpc_dma: Use sizeof(*var) in kzalloc().
Date: Mon, 30 Mar 2020 14:56:05 +0200	[thread overview]
Message-ID: <20200330145605.285d8877@elisabeth> (raw)
In-Reply-To: <1e4819bb3fc9377f19755625518b0cafabaed509.camel@gmail.com>

On Mon, 30 Mar 2020 06:45:00 -0400
Sam Muhammed <jane.pnx9@gmail.com> wrote:

> On Mon, 2020-03-30 at 03:04 +0200, Stefano Brivio wrote:
> > On Wed, 25 Mar 2020 10:26:37 -0400
> > Sam Muhammed <jane.pnx9@gmail.com> wrote:
> >   
> > > kzalloc(sizeof(*var), ...) was the format been used
> > > across the driver, which is the preferred format,
> > > but missed two instances, correct them to match the
> > > coding standards.
> > > 
> > > Checkpatch.pl CHECK: Prefer kzalloc(sizeof(*var)...)
> > > over kzalloc(sizeof(struct var)...)
> > > 
> > > Signed-off-by: Sam Muhammed <jane.pnx9@gmail.com>
> > > ---
> > > Changes in v2:
> > > - Update the log message to be more descriptive.  
> > 
> > It would be nicer to refer here to the person who suggested the change,
> > if it's not you directly noticing the problem (you can just mention
> > them by name, name and surname, or explicitly say "suggested by ...",
> > "requested by ...", etc). There are many recent examples on this list.
> >   
> Ohh, Sorry for that, i thought this tag is more of a code related
> change. since being new to the process, most of the time log messages
> and subject lines will be commented on to follow the conventions. which
> i thought is a different case than changes in the patch itself.

Wait, I wasn't talking about tags here:

- use a Suggested-by: tag if the patch itself was suggested by somebody
  (which is not the case for this patch)

- v2 was prompted by comments you received for v1 by Julia, so it would
  be appropriate to state, in the history of log changes:
	- Update the log message to be more descriptive (suggested by
	  Julia Lawall)

-- 
Stefano



  reply	other threads:[~2020-03-30 12:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 14:26 [PATCH v2 0/7] Staging: kpc2000: kpc_dma: Clear Misc Checkpatch.pl WARNINGS Sam Muhammed
2020-03-25 14:26 ` [PATCH v2 1/7] Staging: kpc2000: kpc_dma: Remove comparison to NULL Sam Muhammed
2020-03-30  1:04   ` [Outreachy kernel] " Stefano Brivio
2020-03-30 10:48     ` Sam Muhammed
2020-03-30 10:58       ` Julia Lawall
2020-03-30 11:02         ` Sam Muhammed
2020-03-30 13:55       ` Stefano Brivio
2020-03-30 16:33         ` Sam Muhammed
2020-03-25 14:26 ` [PATCH v2 2/7] Staging: kpc2000: kpc_dma: Use sizeof(*var) in kzalloc() Sam Muhammed
2020-03-30  1:04   ` [Outreachy kernel] " Stefano Brivio
2020-03-30 10:45     ` Sam Muhammed
2020-03-30 12:56       ` Stefano Brivio [this message]
2020-03-30 13:10         ` Sam Muhammed
2020-03-30 13:51           ` Stefano Brivio
2020-03-25 14:26 ` [PATCH v2 3/7] Staging: kpc2000: kpc_dma: Remove unnecessary braces Sam Muhammed
2020-03-25 14:26 ` [PATCH v2 4/7] Staging: kpc2000: kpc_dma: Include the preferred header Sam Muhammed
2020-03-25 14:26 ` [PATCH v2 5/7] Staging: kpc2000: kpc_dma: Use the SPDK comment style Sam Muhammed
2020-03-25 14:26 ` [PATCH v2 6/7] Staging: kpc2000: kpc_dma: Use kcalloc over kzalloc Sam Muhammed
2020-03-25 14:26 ` [PATCH v2 7/7] Staging: kpc2000: kpc_dma: Use spaces around operators Sam Muhammed
2020-03-30  1:04 ` [Outreachy kernel] [PATCH v2 0/7] Staging: kpc2000: kpc_dma: Clear Misc Checkpatch.pl WARNINGS Stefano Brivio

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=20200330145605.285d8877@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jane.pnx9@gmail.com \
    --cc=outreachy-kernel@googlegroups.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 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.