Can you send patch with this information in commit msg?
On Thu, Jan 31, 2019 at 3:32 AM Eli Britstein wrote:
>
> ping
>
> for the using patch, i put below the v1 of it. here is v2:
>
> https://patchwork.ozlabs.org/patch/1023406/
>
>
> On 1/27/2019 8:37 AM, Eli Britstein wrote:
> >
> > On
ping
for the using patch, i put below the v1 of it. here is v2:
https://patchwork.ozlabs.org/patch/1023406/
On 1/27/2019 8:37 AM, Eli Britstein wrote:
>
> On 1/27/2019 1:04 AM, David Miller wrote:
>> From: Eli Britstein
>> Date: Thu, 24 Jan 2019 11:46:47 +0200
>>
>>> Declare ovs key
On 1/27/2019 1:04 AM, David Miller wrote:
> From: Eli Britstein
> Date: Thu, 24 Jan 2019 11:46:47 +0200
>
>> Declare ovs key structures using macros to enable retrieving fields
>> information, with no functional change.
>>
>> Signed-off-by: Eli Britstein
>> Reviewed-by: Roi Dayan
> I agree
From: Eli Britstein
Date: Thu, 24 Jan 2019 11:46:47 +0200
> Declare ovs key structures using macros to enable retrieving fields
> information, with no functional change.
>
> Signed-off-by: Eli Britstein
> Reviewed-by: Roi Dayan
I agree with Pravin, this need a much better commit message.
On Thu, Jan 24, 2019 at 1:47 AM Eli Britstein wrote:
>
> Declare ovs key structures using macros to enable retrieving fields
> information, with no functional change.
>
I am not sure why is this done. Can you explain what are u trying to solve here?
> Signed-off-by: Eli Britstein
>
Declare ovs key structures using macros to enable retrieving fields
information, with no functional change.
Signed-off-by: Eli Britstein
Reviewed-by: Roi Dayan
---
include/uapi/linux/openvswitch.h | 102 ++-
1 file changed, 69 insertions(+), 33 deletions(-)
