From: YueHaibing <yuehaibing@huawei.com> To: Luciano Coelho <luciano.coelho@intel.com>, Johannes Berg <johannes.berg@intel.com>, Emmanuel Grumbach <emmanuel.grumbach@intel.com>, Intel Linux Wireless <linuxwifi@intel.com>, Kalle Valo <kvalo@codeaurora.org> Cc: <linux-wireless@vger.kernel.org>, <kernel-janitors@vger.kernel.org> Subject: Re: [PATCH] iwlwifi: acpi: Use kmemdup rather than duplicating its implementation in iwl_parse_nvm_mcc_info Date: Wed, 17 Oct 2018 15:48:15 +0800 [thread overview] Message-ID: <a3ce52c5-c3d8-a06e-6f97-6b40d2906e4a@huawei.com> (raw) In-Reply-To: <4016573ae1c44a37bbf98c1225c02afd8b82e713.camel@intel.com> On 2018/10/17 15:25, Luciano Coelho wrote: > On Fri, 2018-10-05 at 09:02 +0000, YueHaibing wrote: >> Use kmemdup rather than duplicating its implementation >> >> Signed-off-by: YueHaibing <yuehaibing@huawei.com> >> --- > > Thanks, YueHaibing. I have applied this in our internal tree and it > will eventually reach the mainline, following our normal upstreaming > process. > > I have modified the subject and the commit message a bit. Thanks you! > > -- > Cheers, > Luca. > > > . >
WARNING: multiple messages have this Message-ID (diff)
From: YueHaibing <yuehaibing@huawei.com> To: Luciano Coelho <luciano.coelho@intel.com>, Johannes Berg <johannes.berg@intel.com>, Emmanuel Grumbach <emmanuel.grumbach@intel.com>, Intel Linux Wireless <linuxwifi@intel.com>, Kalle Valo <kvalo@codeaurora.org> Cc: linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org Subject: Re: [PATCH] iwlwifi: acpi: Use kmemdup rather than duplicating its implementation in iwl_parse_nvm_m Date: Wed, 17 Oct 2018 07:48:15 +0000 [thread overview] Message-ID: <a3ce52c5-c3d8-a06e-6f97-6b40d2906e4a@huawei.com> (raw) In-Reply-To: <4016573ae1c44a37bbf98c1225c02afd8b82e713.camel@intel.com> On 2018/10/17 15:25, Luciano Coelho wrote: > On Fri, 2018-10-05 at 09:02 +0000, YueHaibing wrote: >> Use kmemdup rather than duplicating its implementation >> >> Signed-off-by: YueHaibing <yuehaibing@huawei.com> >> --- > > Thanks, YueHaibing. I have applied this in our internal tree and it > will eventually reach the mainline, following our normal upstreaming > process. > > I have modified the subject and the commit message a bit. Thanks you! > > -- > Cheers, > Luca. > > > . >
next prev parent reply other threads:[~2018-10-17 7:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-05 8:51 [PATCH] iwlwifi: acpi: Use kmemdup rather than duplicating its implementation in iwl_parse_nvm_mcc_i YueHaibing 2018-10-05 9:02 ` [PATCH] iwlwifi: acpi: Use kmemdup rather than duplicating its implementation in iwl_parse_nvm_mcc_info YueHaibing 2018-10-17 7:25 ` Luciano Coelho 2018-10-17 7:25 ` [PATCH] iwlwifi: acpi: Use kmemdup rather than duplicating its implementation in iwl_parse_nvm_m Luciano Coelho 2018-10-17 7:48 ` YueHaibing [this message] 2018-10-17 7:48 ` YueHaibing
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=a3ce52c5-c3d8-a06e-6f97-6b40d2906e4a@huawei.com \ --to=yuehaibing@huawei.com \ --cc=emmanuel.grumbach@intel.com \ --cc=johannes.berg@intel.com \ --cc=kernel-janitors@vger.kernel.org \ --cc=kvalo@codeaurora.org \ --cc=linux-wireless@vger.kernel.org \ --cc=linuxwifi@intel.com \ --cc=luciano.coelho@intel.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: linkBe 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.