All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Mao Wenan <maowenan@huawei.com>
Cc: amitkarwar@gmail.com, nishants@marvell.com, gbhat@marvell.com,
	huxinming820@gmail.com, linux-wireless@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH wireless-drivers-next v2] mwifiex: use eth_broadcast_addr() to assign broadcast address
Date: Wed, 24 Jul 2019 11:56:24 +0000	[thread overview]
Message-ID: <20190724115624.85D4660237@smtp.codeaurora.org> (raw)
In-Reply-To: <20190724062545.119041-1-maowenan@huawei.com>

Mao Wenan <maowenan@huawei.com> wrote:

> This patch is to use eth_broadcast_addr() to assign broadcast address
> insetad of memcpy().
> 
> Signed-off-by: Mao Wenan <maowenan@huawei.com>

Patch applied to wireless-drivers-next.git, thanks.

15e830e90fde mwifiex: use eth_broadcast_addr() to assign broadcast address

-- 
https://patchwork.kernel.org/patch/11056129/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Mao Wenan <maowenan@huawei.com>
Cc: <amitkarwar@gmail.com>, <nishants@marvell.com>,
	<gbhat@marvell.com>, <huxinming820@gmail.com>,
	<linux-wireless@vger.kernel.org>,
	<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH wireless-drivers-next v2] mwifiex: use eth_broadcast_addr() to assign broadcast address
Date: Wed, 24 Jul 2019 11:56:24 +0000 (UTC)	[thread overview]
Message-ID: <20190724115624.85D4660237@smtp.codeaurora.org> (raw)
In-Reply-To: <20190724062545.119041-1-maowenan@huawei.com>

Mao Wenan <maowenan@huawei.com> wrote:

> This patch is to use eth_broadcast_addr() to assign broadcast address
> insetad of memcpy().
> 
> Signed-off-by: Mao Wenan <maowenan@huawei.com>

Patch applied to wireless-drivers-next.git, thanks.

15e830e90fde mwifiex: use eth_broadcast_addr() to assign broadcast address

-- 
https://patchwork.kernel.org/patch/11056129/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2019-07-24 11:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10  7:25 [net-next] mwifiex: use eth_broadcast_addr() to assign broadcast address Mao Wenan
2019-07-10  7:25 ` Mao Wenan
2019-07-24  1:32 ` maowenan
2019-07-24  1:32   ` maowenan
2019-07-24  5:42   ` Kalle Valo
2019-07-24  5:42     ` Kalle Valo
2019-07-24  6:25     ` [PATCH wireless-drivers-next v2] " Mao Wenan
2019-07-24  6:25       ` Mao Wenan
2019-07-24 11:56       ` Kalle Valo [this message]
2019-07-24 11:56         ` Kalle Valo

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=20190724115624.85D4660237@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=amitkarwar@gmail.com \
    --cc=gbhat@marvell.com \
    --cc=huxinming820@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maowenan@huawei.com \
    --cc=nishants@marvell.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.