All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Min Hu (Connor)" <humin29@huawei.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Stephen Hemminger <stephen@networkplumber.org>, <dev@dpdk.org>,
	<ferruh.yigit@intel.com>
Subject: Re: [PATCH] kni: fix device address set
Date: Thu, 7 Apr 2022 16:08:34 +0800	[thread overview]
Message-ID: <81d69f4b-4d1f-6432-8d1f-c771fc2d8cb5@huawei.com> (raw)
In-Reply-To: <2364580.jE0xQCEvom@thomas>

OK, I see, thanks Thomas.

在 2022/4/7 15:42, Thomas Monjalon 写道:
> 07/04/2022 02:44, Min Hu (Connor):
>> Hi, Stephen,
>>    I think this is a good option, but the macro definition is like:
>> +#if LINUX_VERSION_CODE < KERNEL_VERSION(3, 14, 0)
>> +#define ether_addr_copy(dst, src) memcpy(dst, src, ETH_ALEN)
>> +#endif
>>
>> @Ferry, why is it limited for "LINUX_VERSION_CODE < KERNEL_VERSION(3,
>> 14, 0)" ?
> 
> I guess that's because it is defined in "new kernels" so we need
> a definition in DPDK for old kernels.
> 
> 
> 
> .
> 

  reply	other threads:[~2022-04-07  8:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  8:22 [PATCH] kni: fix device address set Min Hu (Connor)
2022-04-06 15:17 ` Stephen Hemminger
2022-04-07  0:44   ` Min Hu (Connor)
2022-04-07  3:18     ` Stephen Hemminger
2022-04-07  6:21       ` Min Hu (Connor)
2022-04-07  7:42     ` Thomas Monjalon
2022-04-07  8:08       ` Min Hu (Connor) [this message]
2022-04-07  8:25 ` [PATCH v2] " Min Hu (Connor)
2022-04-25  3:58   ` Min Hu (Connor)
2022-05-23  9:24 ` [PATCH v3] " Min Hu (Connor)
2022-05-31 15:32   ` Andrew Rybchenko
2022-06-01  2:01     ` Min Hu (Connor)
2022-06-01  1:59 ` [PATCH v4] " Min Hu (Connor)
2022-06-01  9:02   ` Andrew Rybchenko
2022-06-02  6:58     ` Min Hu (Connor)
2022-06-02  6:54 ` [PATCH v5] " Min Hu (Connor)
2022-06-03 11:50   ` Andrew Rybchenko
2022-06-02 15:31 ` [PATCH] " Stephen Hemminger

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=81d69f4b-4d1f-6432-8d1f-c771fc2d8cb5@huawei.com \
    --to=humin29@huawei.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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.