From: Greg KH <gregkh@linuxfoundation.org>
To: Liuye <liu.yeC@h3c.com>
Cc: "daniel.thompson@linaro.org" <daniel.thompson@linaro.org>,
"dianders@chromium.org" <dianders@chromium.org>,
"jason.wessel@windriver.com" <jason.wessel@windriver.com>,
"jirislaby@kernel.org" <jirislaby@kernel.org>,
"kgdb-bugreport@lists.sourceforge.net"
<kgdb-bugreport@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>
Subject: Re: Re: Re：[PATCH V11] kdb: Fix the deadlock issue in KDB debugging.
Date: Fri, 19 Apr 2024 08:06:42 +0200 [thread overview]
Message-ID: <2024041915-flinch-cinema-9c22@gregkh> (raw)
In-Reply-To: <ac27269989394d8dac859763bc7578d6@h3c.com>
On Fri, Apr 19, 2024 at 05:54:58AM +0000, Liuye wrote:
> @Greg KH
>
> This issue still needs to be resolved, but I don't know how to do it.
> Please tell me an effective strategy. How should feedback be given to make it effective for you?
> There is already an approval process for external emails in the current company.
> And a review mechanism has been added within the team. And internal training is provided.
> The previous mentioned has been completed. What else needs to be done?
What would you want to see if you were in my position here?
Some sort of "proof" that this really is the case? A discussion with
your company legal group about this? A discussion with your legal group
and the open source legal community about how they have structured all
of this so that it will not happen again and a discussion about how this
did happen (i.e. a blameless post-mortum)? A signed-off-by on your next
patch from a lawyer in that group?
In other words, what does your legal group think would be sufficient
here?
thanks,
greg k-h
prev parent reply other threads:[~2024-04-19 6:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 5:54 Re: Re：[PATCH V11] kdb: Fix the deadlock issue in KDB debugging Liuye
2024-04-19 6:06 ` Greg KH [this message]
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=2024041915-flinch-cinema-9c22@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=jirislaby@kernel.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=liu.yeC@h3c.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).