All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Kenneth Lee <klee33@uw.edu>
Cc: bcousson@baylibre.com, paul@pwsan.com,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP2+: hwmod: Use kzalloc for allocating only one element
Date: Tue, 28 Mar 2023 08:46:15 +0300	[thread overview]
Message-ID: <20230328054615.GM7501@atomide.com> (raw)
In-Reply-To: <20220809072050.1733996-1-klee33@uw.edu>

* Kenneth Lee <klee33@uw.edu> [220809 10:14]:
> Use kzalloc(...) rather than kcalloc(1, ...) because the number of
> elements we are specifying in this case is 1, so kzalloc would
> accomplish the same thing and we can simplify.

Thanks applying into omap-for-v6.4/cleanup.

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Kenneth Lee <klee33@uw.edu>
Cc: bcousson@baylibre.com, paul@pwsan.com,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP2+: hwmod: Use kzalloc for allocating only one element
Date: Tue, 28 Mar 2023 08:46:15 +0300	[thread overview]
Message-ID: <20230328054615.GM7501@atomide.com> (raw)
In-Reply-To: <20220809072050.1733996-1-klee33@uw.edu>

* Kenneth Lee <klee33@uw.edu> [220809 10:14]:
> Use kzalloc(...) rather than kcalloc(1, ...) because the number of
> elements we are specifying in this case is 1, so kzalloc would
> accomplish the same thing and we can simplify.

Thanks applying into omap-for-v6.4/cleanup.

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-03-28  5:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09  7:20 [PATCH] ARM: OMAP2+: hwmod: Use kzalloc for allocating only one element Kenneth Lee
2022-08-09  7:20 ` Kenneth Lee
2023-03-28  5:46 ` Tony Lindgren [this message]
2023-03-28  5:46   ` Tony Lindgren

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=20230328054615.GM7501@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=klee33@uw.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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.