All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: patches@opensource.wolfsonmicro.com,
	Chanwoo Choi <cw00.choi@samsung.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: extcon: arizona: Use devm_kcalloc() in arizona_extcon_get_micd_configs()
Date: Wed, 26 Apr 2017 08:01:47 +0000	[thread overview]
Message-ID: <20170426080147.GH1594@localhost.localdomain> (raw)
In-Reply-To: <b5bb4d25-6cfd-5019-bfbd-dff90c1f9bc1@users.sourceforge.net>

On Mon, Apr 24, 2017 at 03:34:07PM +0200, SF Markus Elfring wrote:
> > Actually fixes a bug on the alloc as well looks like the type was
> > wrong before.
> 
> Does your feedback mean that the tag “Fixes” should be added
> to this update suggestion?
> 

I am happy with it as is, but there would certainly be nothing
wrong with a fixes tag.

Thanks,
Charles

WARNING: multiple messages have this Message-ID (diff)
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: <patches@opensource.wolfsonmicro.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	LKML <linux-kernel@vger.kernel.org>,
	<kernel-janitors@vger.kernel.org>
Subject: Re: extcon: arizona: Use devm_kcalloc() in arizona_extcon_get_micd_configs()
Date: Wed, 26 Apr 2017 09:01:47 +0100	[thread overview]
Message-ID: <20170426080147.GH1594@localhost.localdomain> (raw)
In-Reply-To: <b5bb4d25-6cfd-5019-bfbd-dff90c1f9bc1@users.sourceforge.net>

On Mon, Apr 24, 2017 at 03:34:07PM +0200, SF Markus Elfring wrote:
> > Actually fixes a bug on the alloc as well looks like the type was
> > wrong before.
> 
> Does your feedback mean that the tag “Fixes” should be added
> to this update suggestion?
> 

I am happy with it as is, but there would certainly be nothing
wrong with a fixes tag.

Thanks,
Charles

  reply	other threads:[~2017-04-26  8:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170424123857epcas2p24390d04885c9fc4c1980838ed8a4db06@epcas2p2.samsung.com>
2017-04-24 12:38 ` [PATCH 0/3] Extcon: Fine-tuning for three functions SF Markus Elfring
2017-04-24 12:38   ` SF Markus Elfring
2017-04-24 12:40   ` [PATCH 1/3] extcon: Use devm_kcalloc() in extcon_dev_register() SF Markus Elfring
2017-04-24 12:40     ` SF Markus Elfring
2017-04-24 12:41   ` [PATCH 2/3] extcon: Fix a typo in three comment lines SF Markus Elfring
2017-04-24 12:41     ` SF Markus Elfring
2017-04-24 12:43   ` [PATCH 3/3] extcon: arizona: Use devm_kcalloc() in arizona_extcon_get_micd_configs() SF Markus Elfring
2017-04-24 12:43     ` SF Markus Elfring
2017-04-24 12:59     ` Charles Keepax
2017-04-24 13:00       ` Charles Keepax
2017-04-24 13:34       ` SF Markus Elfring
2017-04-24 13:34         ` SF Markus Elfring
2017-04-26  8:01         ` Charles Keepax [this message]
2017-04-26  8:01           ` Charles Keepax
2017-05-23  9:34   ` [PATCH 0/3] Extcon: Fine-tuning for three functions Chanwoo Choi
2017-05-23  9:34     ` Chanwoo Choi

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=20170426080147.GH1594@localhost.localdomain \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=cw00.choi@samsung.com \
    --cc=elfring@users.sourceforge.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=patches@opensource.wolfsonmicro.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.