netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yingjie Wang" <wangyingjie55@126.com>
To: "Jakub Kicinski" <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH v2] af/rvu_cgx: Fix missing check bugs in rvu_cgx.c
Date: Wed, 13 Jan 2021 21:27:35 +0800 (CST)	[thread overview]
Message-ID: <355954d9.5264.176fbee1ed6.Coremail.wangyingjie55@126.com> (raw)
In-Reply-To: <20210112181328.091f7cfb@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

Thanks for your reply.  I commit this change on linux-next/stable branch, and I use "git log --pretty=fixes" command to get the Fixes tag. I want to know if I need to make a change on any other branch and commit it?
At 2021-01-13 10:13:28, "Jakub Kicinski" <kuba@kernel.org> wrote:
>On Mon, 11 Jan 2021 18:09:49 -0800 wangyingjie55@126.com wrote:
>> From: Yingjie Wang <wangyingjie55@126.com>
>> 
>> In rvu_mbox_handler_cgx_mac_addr_get()
>> and rvu_mbox_handler_cgx_mac_addr_set(),
>> the msg is expected only from PFs that are mapped to CGX LMACs.
>> It should be checked before mapping,
>> so we add the is_cgx_config_permitted() in the functions.
>> 
>> Fixes: 289e20bc1ab5 ("af/rvu_cgx: Fix missing check bugs in rvu_cgx.c")
>> Signed-off-by: Yingjie Wang <wangyingjie55@126.com>
>
>
>Fixes tag: Fixes: 289e20bc1ab5 ("af/rvu_cgx: Fix missing check bugs in rvu_cgx.c")
>Has these problem(s):
>	- Target SHA1 does not exist
>
>Where is that commit from? You're not referring to this commit itself
>in your tree? The subject is suspiciously similar :S

  reply	other threads:[~2021-01-13 20:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12  2:09 [PATCH v2] af/rvu_cgx: Fix missing check bugs in rvu_cgx.c wangyingjie55
2021-01-13  2:13 ` Jakub Kicinski
2021-01-13 13:27   ` Yingjie Wang [this message]
2021-01-13 23:35     ` Jakub Kicinski

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=355954d9.5264.176fbee1ed6.Coremail.wangyingjie55@126.com \
    --to=wangyingjie55@126.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).