All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang Yingliang <yangyingliang@huawei.com>
To: Guenter Roeck <linux@roeck-us.net>, Heiko Carstens <hca@linux.ibm.com>
Cc: <linux-watchdog@vger.kernel.org>, <wim@linux-watchdog.org>,
	<yangyingliang@huawei.com>
Subject: Re: [PATCH -next] watchdog: diag288_wdt: use kmemdup() to allocate memory
Date: Fri, 3 Feb 2023 10:40:31 +0800	[thread overview]
Message-ID: <e67f5e87-6fc6-9e16-7354-6fa8464e0b46@huawei.com> (raw)
In-Reply-To: <6f80303d-fe26-a2af-a1fa-e99c00da9a81@roeck-us.net>


On 2023/2/2 21:35, Guenter Roeck wrote:
> On 2/2/23 05:22, Heiko Carstens wrote:
>> On Thu, Feb 02, 2023 at 03:41:27PM +0800, Yang Yingliang wrote:
>>> Use kmemdup() helper instead of open-coding to simplify
>>> the code when allocating ebc_cmd.
>>>
>>> Generated by: scripts/coccinelle/api/memdup.cocci
>>>
>>> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
>>> ---
>>>   drivers/watchdog/diag288_wdt.c | 3 +--
>>>   1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> Thanks, but this code will be changed differently with the next merge
>> window. Therefore I will not apply patch.
>
> It looks like you decided to bypass even sending your patches to the 
> watchdog
> mailing list. I know I have not been as responsive there as I should be,
> but that it no reason to bypass the maintainers completely.
I sent the patch to all the maintainers that get by 
'./scripts/get_maintainer.pl drivers/watchdog/diag288_wdt.c'

Thanks,
Yang
>
> Guenter
>
> .

  parent reply	other threads:[~2023-02-03  2:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02  7:41 [PATCH -next] watchdog: diag288_wdt: use kmemdup() to allocate memory Yang Yingliang
2023-02-02 13:22 ` Heiko Carstens
2023-02-02 13:35   ` Guenter Roeck
2023-02-02 14:06     ` Heiko Carstens
2023-02-02 15:41       ` Guenter Roeck
2023-02-03  2:40     ` Yang Yingliang [this message]
2023-02-03  4:52       ` Guenter Roeck

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=e67f5e87-6fc6-9e16-7354-6fa8464e0b46@huawei.com \
    --to=yangyingliang@huawei.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=wim@linux-watchdog.org \
    /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.