| Message ID | 20250226140343.3907080-26-alex.bennee@linaro.org (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | maintainer updates for 10.0 softfreeze (gpu/tcg tests, plugins, MAINTAINERS) | expand |
Hi, A bit offtopic: we just received patches from Syntacore [1]. Syntacore does not appear in the US sanction list website, but in a Google search I found out that Syntacore was acquired by Yadro in 2019, i.e. Yadro is its parent organization. And Yadro has been sanctioned. Does anybody know the rule in this case? If a parent company is sanctioned does that cascade to all its subsidiaries? I have no idea whether we can engage with these patches or not. Thanks, Daniel [1] https://lore.kernel.org/qemu-riscv/20250227144200.69270-1-saveliy.motov@syntacore.com/ On 2/26/25 11:03 AM, Alex Bennée wrote: > The following organisations appear on the US sanctions list: > > Yadro: https://sanctionssearch.ofac.treas.gov/Details.aspx?id=41125 > ISPRAS: https://sanctionssearch.ofac.treas.gov/Details.aspx?id=50890 > > As a result maintainers interacting with such entities would face > legal risk in a number of jurisdictions. To reduce the risk of > inadvertent non-compliance remove entries from these organisations > from the MAINTAINERS file. > > Mark the pcf8574 system as orphaned until someone volunteers to step > up as a maintainer. Add myself as a second reviewer to record/replay > so I can help with what odd fixes I can. > > Reviewed-by: Markus Armbruster <armbru@redhat.com> > Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> > Acked-by: Paolo Bonzini <pbonzini@redhat.com> > Signed-off-by: Alex Bennée <alex.bennee@linaro.org> > Message-Id: <20250221161443.2321327-1-alex.bennee@linaro.org> > --- > MAINTAINERS | 7 +++---- > 1 file changed, 3 insertions(+), 4 deletions(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 1911949526..9cdfe19115 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -2529,8 +2529,7 @@ F: hw/i2c/i2c_mux_pca954x.c > F: include/hw/i2c/i2c_mux_pca954x.h > > pcf8574 > -M: Dmitrii Sharikhin <d.sharikhin@yadro.com> > -S: Maintained > +S: Orphaned > F: hw/gpio/pcf8574.c > F: include/gpio/pcf8574.h > > @@ -3627,10 +3626,10 @@ F: net/filter-mirror.c > F: tests/qtest/test-filter* > > Record/replay > -M: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru> > R: Paolo Bonzini <pbonzini@redhat.com> > +R: Alex Bennée <alex.bennee@linaro.org> > W: https://wiki.qemu.org/Features/record-replay > -S: Supported > +S: Odd Fixes > F: replay/* > F: block/blkreplay.c > F: net/filter-replay.c
Daniel Henrique Barboza <dbarboza@ventanamicro.com> writes: > Hi, > > A bit offtopic: we just received patches from Syntacore [1]. Syntacore > does not appear in the US sanction list website, but in a Google search > I found out that Syntacore was acquired by Yadro in 2019, i.e. Yadro is > its parent organization. And Yadro has been sanctioned. > > Does anybody know the rule in this case? If a parent company is sanctioned > does that cascade to all its subsidiaries? I have no idea whether we can engage > with these patches or not. I don't think anyone here can offer any legal advice. We did reach out to the SFC they never replied directly. They did however publish the following blog post: https://sfconservancy.org/blog/2024/dec/12/linux-banned-russian-contributors-do-i-need-to/ but you should probably check with your own orgs lawyers about what you should do. We have additional email domains blocked from our mail servers to avoid accidental interaction but they don't interact with MAINTAINERS which was the motivating factor for this patch (because of processing PRs and automatic cc's from get_maintainers.pl). > > > Thanks, > > Daniel > > > [1] https://lore.kernel.org/qemu-riscv/20250227144200.69270-1-saveliy.motov@syntacore.com/ > > > > On 2/26/25 11:03 AM, Alex Bennée wrote: >> The following organisations appear on the US sanctions list: >> Yadro: >> https://sanctionssearch.ofac.treas.gov/Details.aspx?id=41125 >> ISPRAS: https://sanctionssearch.ofac.treas.gov/Details.aspx?id=50890 >> As a result maintainers interacting with such entities would face >> legal risk in a number of jurisdictions. To reduce the risk of >> inadvertent non-compliance remove entries from these organisations >> from the MAINTAINERS file. >> Mark the pcf8574 system as orphaned until someone volunteers to step >> up as a maintainer. Add myself as a second reviewer to record/replay >> so I can help with what odd fixes I can. >> Reviewed-by: Markus Armbruster <armbru@redhat.com> >> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> >> Acked-by: Paolo Bonzini <pbonzini@redhat.com> >> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> >> Message-Id: <20250221161443.2321327-1-alex.bennee@linaro.org> >> --- >> MAINTAINERS | 7 +++---- >> 1 file changed, 3 insertions(+), 4 deletions(-) >> diff --git a/MAINTAINERS b/MAINTAINERS >> index 1911949526..9cdfe19115 100644 >> --- a/MAINTAINERS >> +++ b/MAINTAINERS >> @@ -2529,8 +2529,7 @@ F: hw/i2c/i2c_mux_pca954x.c >> F: include/hw/i2c/i2c_mux_pca954x.h >> pcf8574 >> -M: Dmitrii Sharikhin <d.sharikhin@yadro.com> >> -S: Maintained >> +S: Orphaned >> F: hw/gpio/pcf8574.c >> F: include/gpio/pcf8574.h >> @@ -3627,10 +3626,10 @@ F: net/filter-mirror.c >> F: tests/qtest/test-filter* >> Record/replay >> -M: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru> >> R: Paolo Bonzini <pbonzini@redhat.com> >> +R: Alex Bennée <alex.bennee@linaro.org> >> W: https://wiki.qemu.org/Features/record-replay >> -S: Supported >> +S: Odd Fixes >> F: replay/* >> F: block/blkreplay.c >> F: net/filter-replay.c
diff --git a/MAINTAINERS b/MAINTAINERS index 1911949526..9cdfe19115 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2529,8 +2529,7 @@ F: hw/i2c/i2c_mux_pca954x.c F: include/hw/i2c/i2c_mux_pca954x.h pcf8574 -M: Dmitrii Sharikhin <d.sharikhin@yadro.com> -S: Maintained +S: Orphaned F: hw/gpio/pcf8574.c F: include/gpio/pcf8574.h @@ -3627,10 +3626,10 @@ F: net/filter-mirror.c F: tests/qtest/test-filter* Record/replay -M: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru> R: Paolo Bonzini <pbonzini@redhat.com> +R: Alex Bennée <alex.bennee@linaro.org> W: https://wiki.qemu.org/Features/record-replay -S: Supported +S: Odd Fixes F: replay/* F: block/blkreplay.c F: net/filter-replay.c