contact
We are reaching you once again as regards the estate of Late George Brumley, you were made one of the beneficiaries of his estate. Do get back to me at your earliest convenience. The Trustees
[PATCH] treewide: update my contact info
Signed-off-by: Miguel Ojeda
---
.mailmap| 1 +
CREDITS | 9 +++--
Documentation/admin-guide/auxdisplay/cfag12864b.rst | 2 +-
Documentation/admin-guide/auxdisplay/ks0108.rst | 2 +-
MAINTAINERS | 12 ++--
drivers/auxdisplay/cfag12864b.c | 4 ++--
drivers/auxdisplay/cfag12864bfb.c | 4 ++--
drivers/auxdisplay/ks0108.c | 4 ++--
include/linux/cfag12864b.h | 2 +-
include/linux/ks0108.h | 2 +-
samples/auxdisplay/cfag12864b-example.c | 2 +-
11 files changed, 21 insertions(+), 23 deletions(-)
diff --git a/.mailmap b/.mailmap
index cc4e91d3075e..132580897fbc 100644
--- a/.mailmap
+++ b/.mailmap
@@ -232,6 +232,7 @@ Maxime Ripard
Mayuresh Janorkar
Michael Buesch
Michel Dänzer
+Miguel Ojeda
Mike Rapoport
Mike Rapoport
Mike Rapoport
diff --git a/CREDITS b/CREDITS
index 9add7e6a4fa0..e8eaf9b373d7 100644
--- a/CREDITS
+++ b/CREDITS
@@ -2841,14 +2841,11 @@ S: Subiaco, 6008
S: Perth, Western Australia
S: Australia
-N: Miguel Ojeda Sandonis
-E: miguel.ojeda.sando...@gmail.com
-W: http://miguelojeda.es
-W: http://jair.lab.fi.uva.es/~migojed/
+N: Miguel Ojeda
+E: oj...@kernel.org
+W: https://ojeda.dev
D: Author of the ks0108, cfag12864b and cfag12864bfb auxiliary display drivers.
D: Maintainer of the auxiliary display drivers tree (drivers/auxdisplay/*)
-S: C/ Mieses 20, 9-B
-S: Valladolid 47009
S: Spain
N: Peter Oruba
diff --git a/Documentation/admin-guide/auxdisplay/cfag12864b.rst
b/Documentation/admin-guide/auxdisplay/cfag12864b.rst
index 18c2865bd322..da385d851acc 100644
--- a/Documentation/admin-guide/auxdisplay/cfag12864b.rst
+++ b/Documentation/admin-guide/auxdisplay/cfag12864b.rst
@@ -3,7 +3,7 @@ cfag12864b LCD Driver Documentation
===
:License: GPLv2
-:Author & Maintainer: Miguel Ojeda Sandonis
+:Author & Maintainer: Miguel Ojeda
:Date: 2006-10-27
diff --git a/Documentation/admin-guide/auxdisplay/ks0108.rst
b/Documentation/admin-guide/auxdisplay/ks0108.rst
index c0b7faf73136..a7d3fe509373 100644
--- a/Documentation/admin-guide/auxdisplay/ks0108.rst
+++ b/Documentation/admin-guide/auxdisplay/ks0108.rst
@@ -3,7 +3,7 @@ ks0108 LCD Controller Driver Documentation
==
:License: GPLv2
-:Author & Maintainer: Miguel Ojeda Sandonis
+:Author & Maintainer: Miguel Ojeda
:Date: 2006-10-27
diff --git a/MAINTAINERS b/MAINTAINERS
index d3e847f7f3dc..11542312e4e8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3018,7 +3018,7 @@ F:include/uapi/linux/audit.h
F: kernel/audit*
AUXILIARY DISPLAY DRIVERS
-M: Miguel Ojeda Sandonis
+M: Miguel Ojeda
S: Maintained
F: drivers/auxdisplay/
F: include/linux/cfag12864b.h
@@ -4123,13 +4123,13 @@ F: scripts/extract-cert.c
F: scripts/sign-file.c
CFAG12864B LCD DRIVER
-M: Miguel Ojeda Sandonis
+M: Miguel Ojeda
S: Maintained
F: drivers/auxdisplay/cfag12864b.c
F: include/linux/cfag12864b.h
CFAG12864BFB LCD FRAMEBUFFER DRIVER
-M: Miguel Ojeda Sandonis
+M: Miguel Ojeda
S: Maintained
F: drivers/auxdisplay/cfag12864bfb.c
F: include/linux/cfag12864b.h
@@ -4299,7 +4299,7 @@ S:Supported
F: drivers/infiniband/hw/usnic/
CLANG-FORMAT FILE
-M: Miguel Ojeda
+M: Miguel Ojeda
S: Maintained
F: .clang-format
@@ -4441,7 +4441,7 @@ S:Maintained
F: drivers/platform/x86/compal-laptop.c
COMPILER ATTRIBUTES
-M: Miguel Ojeda
+M: Miguel Ojeda
S: Maintained
F: include/linux/compiler_attributes.h
@@ -9903,7 +9903,7 @@ F:include/linux/kprobes.h
F: kernel/kprobes.c
KS0108 LCD CONTROLLER DRIVER
-M: Miguel Ojeda Sandonis
+M: Miguel Ojeda
S: Maintained
F: Documentation/admin-guide/auxdisplay/ks0108.rst
F: drivers/auxdisplay/ks0108.c
diff --git a/drivers/auxdisplay/cfag12864b.c b/drivers/auxdisplay/cfag12864b.c
index 7eebae7e322c..fd430e6866a1 100644
--- a/drivers/auxdisplay/cfag12864b.c
+++ b/drivers/auxdisplay/cfag12864b.c
@@ -5,7 +5,7 @@
* Description: cfag12864b LCD driver
* Depends: ks0108
*
- * Author: Copyright (C) Miguel Ojeda Sandonis
+ * Author: Copyright (C) Miguel Ojeda
*Date: 2006-10-31
*/
@@ -376,5 +376,5 @@ module_init(cfag12864b_init);
module_exit(cfag12864b_exit);
MODULE_LICENSE("GPL v2");
-MODULE_AUTHOR("Miguel Ojeda Sandonis ");
+MODULE_AUTHOR("Miguel Ojeda ");
MODULE_DESCRIPTION("cfag12864b LCD driver");
diff --git a/drivers/auxdisplay/cfag12864bfb.c
b/drivers/auxdisplay/cfag12864bfb.c
index 2002291ab338..d66821adf453 100644
--- a/drivers/auxdisplay/cfag12864bfb.c
+++
Final contact 02
This is another attempt to reach you as regards the estate of Late George Brumley, you were made one of the beneficiaries of his estate. Do get back to me at your earliest convenience. The Trustees
Re: CONTACT MONEY GRAM FOR YOUR DAILY PAYMENT OF $5,000.00
-- Attention: Beneficiary, This is the second time we are notifying you about your COVID-19 Palliative fund of $1,500,000.00. Be inform that We have been authorized by the United Nations Commission (UNC) to release your COVID-19 Response and Recovery Fund of $1,500,000.00 US Dollars through MoneyGram money transfer. You will be receiving the sum of $5,000.00 daily until the total sum of US $1,500,000.00 is completely transferred to you. Besides,we have already credited your first payment of US$5,000.00 today,therefore,you are advice to contact our director of foreign Remittance Department MR.ROBERT TAIWO and request him to give you the details of your first payment such as money transfer reference Numbers and senders name to enable you pick up your first payment of US$5,000.00 at any MoneyGram office located around you. Kindly contact him through the information stated below for faster process. Contact Person: MR.ROBERT TAIWO E-MAIL: transfermoney...@foxmail.com Tel: (+229) 965 483 88 ( WhatsApp ) REMEMBER TO FORWARD HIM YOUR FULL INFORMATION AS REQUIRED BELOW TO ENABLE HIM LOCATE YOUR PAYMENT FILE AND ATTEND TO YOU IMMEDIATELY. 1. Your Full Name: 2. Address: 3. Age: 4. Occupation: 5. Telephone: 6. Country: NOTE: that the amount to be paid to you is (USD1.500, 000.00), we expect your urgent response to this email to enable us monitor the transaction effectively. Best Regards Mrs. Susan Dansuki.
Re: [PATCH v2] MAINTAINERS: Add the security document to SECURITY CONTACT
On Thu, Aug 27, 2020 at 08:20:29PM +0200, Krzysztof Kozlowski wrote: > When changing the document related to kernel security workflow, notify > the security mailing list as its concerned by this. > > Cc: Greg Kroah-Hartman > Cc: > Signed-off-by: Krzysztof Kozlowski > > --- > > Changes since v1: > 1. Changed order - F: go to end of entry, > 2. Remove embargoed-hardware-issues > --- > MAINTAINERS | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 8107b3d5d6df..19064a4ae9b0 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -15621,6 +15621,7 @@ F:include/uapi/linux/sed* > SECURITY CONTACT > M: Security Officers > S: Supported > +F: Documentation/admin-guide/security-bugs.rst > > SECURITY SUBSYSTEM > M: James Morris > -- > 2.17.1 > Thanks, I'll queue this up in my tree... greg k-h
[PATCH v2] MAINTAINERS: Add the security document to SECURITY CONTACT
When changing the document related to kernel security workflow, notify the security mailing list as its concerned by this. Cc: Greg Kroah-Hartman Cc: Signed-off-by: Krzysztof Kozlowski --- Changes since v1: 1. Changed order - F: go to end of entry, 2. Remove embargoed-hardware-issues --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 8107b3d5d6df..19064a4ae9b0 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -15621,6 +15621,7 @@ F: include/uapi/linux/sed* SECURITY CONTACT M: Security Officers S: Supported +F: Documentation/admin-guide/security-bugs.rst SECURITY SUBSYSTEM M: James Morris -- 2.17.1
Re: [PATCH] MAINTAINERS: Add security docs to SECURITY CONTACT
On Thu, Aug 27, 2020 at 03:20:16PM +0200, Krzysztof Kozlowski wrote: > On Thu, Aug 27, 2020 at 03:18:27PM +0200, Greg Kroah-Hartman wrote: > > On Thu, Aug 27, 2020 at 03:13:30PM +0200, Krzysztof Kozlowski wrote: > > > When changing the documents related to kernel security workflow, notify > > > the security mailing list as its concerned by this. > > > > > > Cc: Greg Kroah-Hartman > > > Signed-off-by: Krzysztof Kozlowski > > > --- > > > MAINTAINERS | 2 ++ > > > 1 file changed, 2 insertions(+) > > > > > > diff --git a/MAINTAINERS b/MAINTAINERS > > > index 8107b3d5d6df..a1e07d0f3205 100644 > > > --- a/MAINTAINERS > > > +++ b/MAINTAINERS > > > @@ -15620,6 +15620,8 @@ F:include/uapi/linux/sed* > > > > > > SECURITY CONTACT > > > M: Security Officers > > > +F: Documentation/admin-guide/security-bugs.rst > > > +F: Documentation/process/embargoed-hardware-issues.rst > > > > The hardware-issues document is "owned" by a different group of > > suckers^Wdevelopers, that is independant of security@k.o, so that file > > shouldn't be added to them here. > > True, but isn't this broader security group involved in designing and > discussing the HW security process? While I think a number of the people did overlap, it was not everyone as the processes are _VERY_ different for obvious reasons. So please keep it separate for now. There is a list of people who care about this document, in the document itself, if anyone ever wants to send changes to it. No need to enumerate them all in the MAINTAINERS file. thanks, greg k-h
Re: [PATCH] MAINTAINERS: Add security docs to SECURITY CONTACT
On Thu, Aug 27, 2020 at 03:13:30PM +0200, Krzysztof Kozlowski wrote: > When changing the documents related to kernel security workflow, notify > the security mailing list as its concerned by this. > > Cc: Greg Kroah-Hartman > Signed-off-by: Krzysztof Kozlowski > --- > MAINTAINERS | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 8107b3d5d6df..a1e07d0f3205 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -15620,6 +15620,8 @@ F: include/uapi/linux/sed* > > SECURITY CONTACT > M: Security Officers > +F: Documentation/admin-guide/security-bugs.rst > +F: Documentation/process/embargoed-hardware-issues.rst The hardware-issues document is "owned" by a different group of suckers^Wdevelopers, that is independant of security@k.o, so that file shouldn't be added to them here. thanks, greg k-h
Re: [PATCH] MAINTAINERS: Add security docs to SECURITY CONTACT
On Thu, Aug 27, 2020 at 03:18:27PM +0200, Greg Kroah-Hartman wrote: > On Thu, Aug 27, 2020 at 03:13:30PM +0200, Krzysztof Kozlowski wrote: > > When changing the documents related to kernel security workflow, notify > > the security mailing list as its concerned by this. > > > > Cc: Greg Kroah-Hartman > > Signed-off-by: Krzysztof Kozlowski > > --- > > MAINTAINERS | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/MAINTAINERS b/MAINTAINERS > > index 8107b3d5d6df..a1e07d0f3205 100644 > > --- a/MAINTAINERS > > +++ b/MAINTAINERS > > @@ -15620,6 +15620,8 @@ F: include/uapi/linux/sed* > > > > SECURITY CONTACT > > M: Security Officers > > +F: Documentation/admin-guide/security-bugs.rst > > +F: Documentation/process/embargoed-hardware-issues.rst > > The hardware-issues document is "owned" by a different group of > suckers^Wdevelopers, that is independant of security@k.o, so that file > shouldn't be added to them here. True, but isn't this broader security group involved in designing and discussing the HW security process? Best regards, Krzysztof
[PATCH] MAINTAINERS: Add security docs to SECURITY CONTACT
When changing the documents related to kernel security workflow, notify the security mailing list as its concerned by this. Cc: Greg Kroah-Hartman Signed-off-by: Krzysztof Kozlowski --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 8107b3d5d6df..a1e07d0f3205 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -15620,6 +15620,8 @@ F: include/uapi/linux/sed* SECURITY CONTACT M: Security Officers +F: Documentation/admin-guide/security-bugs.rst +F: Documentation/process/embargoed-hardware-issues.rst S: Supported SECURITY SUBSYSTEM -- 2.17.1
Re: [PATCH] can: mscan: mpc5xxx_can: update contact email
On Sat, May 02, 2020 at 04:26:56PM +0200, Wolfram Sang wrote: > The 'pengutronix' address is defunct for years. Use the proper contact > address. > > Signed-off-by: Wolfram Sang Ping? > --- > drivers/net/can/mscan/mpc5xxx_can.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/net/can/mscan/mpc5xxx_can.c > b/drivers/net/can/mscan/mpc5xxx_can.c > index e4f4b5c9ebd6..e254e04ae257 100644 > --- a/drivers/net/can/mscan/mpc5xxx_can.c > +++ b/drivers/net/can/mscan/mpc5xxx_can.c > @@ -5,7 +5,7 @@ > * Copyright (C) 2004-2005 Andrey Volkov , > * Varma Electronics Oy > * Copyright (C) 2008-2009 Wolfgang Grandegger > - * Copyright (C) 2009 Wolfram Sang, Pengutronix > + * Copyright (C) 2009 Wolfram Sang, Pengutronix > */ > > #include > -- > 2.20.1 > signature.asc Description: PGP signature
[PATCH] CREDITS: Update contact information
Update my email address in driver, documentation, and add to credits. diff --git a/CREDITS b/CREDITS index 0787b5872906..65803e878c92 100644 --- a/CREDITS +++ b/CREDITS @@ -3957,6 +3957,14 @@ S: 820 4th St. N. S: Fargo, North Dakota 58122 S: USA +N: Neil Whelchel +E: n...@goautomation.biz +W: http://goautomation.biz +S: Go Automation, LLC +S: P.O. Box 2082 +S: Joshua Tree, Ca 92252 +S: USA + N: Steven Whitehouse E: st...@chygwyn.com W: http://www.chygwyn.com/~steve diff --git a/Documentation/usb/usb-serial.rst b/Documentation/usb/usb-serial.rst index 8fa7dbd3da9a..f9ebfb1a60a3 100644 --- a/Documentation/usb/usb-serial.rst +++ b/Documentation/usb/usb-serial.rst @@ -231,7 +231,7 @@ ZyXEL omni.net lcd plus ISDN TA Cypress M8 CY4601 Family Serial Driver -- - This driver was in most part developed by Neil "koyama" Whelchel. It + This driver was in most part developed by Neil Whelchel. It has been improved since that previous form to support dynamic serial line settings and improved line handling. The driver is for the most part stable and has been tested on an smp machine. (dual p2) diff --git a/drivers/usb/serial/cypress_m8.c b/drivers/usb/serial/cypress_m8.c index ecda82198798..2b1d854645ed 100644 --- a/drivers/usb/serial/cypress_m8.c +++ b/drivers/usb/serial/cypress_m8.c @@ -5,7 +5,7 @@ * Copyright (C) 2004 * Lonnie Mendez (dign...@gmail.com) * Copyright (C) 2003,2004 - * Neil Whelchel (koy...@firstlight.net) + * Neil Whelchel (n...@goautomation.biz) * * See Documentation/usb/usb-serial.rst for more information on using this * driver @@ -45,7 +45,7 @@ static bool stats; static int interval; static bool unstable_bauds; -#define DRIVER_AUTHOR "Lonnie Mendez , Neil Whelchel " +#define DRIVER_AUTHOR "Lonnie Mendez , Neil Whelchel " #define DRIVER_DESC "Cypress USB to Serial Driver" /* write buffer size defines */
Re: CONTACT MONEY GRAM FOR YOUR DAILY PAYMENT OF $5,000.00
-- Attention: Beneficiary, This is the second time we are notifying you about your COVID-19 Palliative fund of $1,500,000.00. Be inform that We have been authorized by the United Nations Commission (UNC) to release your COVID-19 Response and Recovery Fund of $1,500,000.00 US Dollars through MoneyGram money transfer. You will be receiving the sum of $5,000.00 daily until the total sum of US $1,500,000.00 is completely transferred to you. Besides,we have already credited your first payment of US$5,000.00 today,therefore,you are advice to contact our director of foreign Remittance Department MR.ROBERT TAIWO and request him to give you the details of your first payment such as money transfer reference Numbers and senders name to enable you pick up your first payment of US$5,000.00 at any MoneyGram office located around you. Kindly contact him through the information stated below for faster process. Contact Person: MR.ROBERT TAIWO E-MAIL: transfermoney...@foxmail.com Tel: (+229) 965 483 88 ( WhatsApp ) REMEMBER TO FORWARD HIM YOUR FULL INFORMATION AS REQUIRED BELOW TO ENABLE HIM LOCATE YOUR PAYMENT FILE AND ATTEND TO YOU IMMEDIATELY. 1. Your Full Name: 2. Address: 3. Age: 4. Occupation: 5. Telephone: 6. Country: NOTE: that the amount to be paid to you is (USD1.500, 000.00), we expect your urgent response to this email to enable us monitor the transaction effectively. Best Regards Mrs. Susan Dansuki.
It Is My Great Pleasure To Contact You
Dear Friend, Greetings and Nice Day. Assalamu Alaikum May i use this medium to open a mutual communication with you seeking your acceptance towards investing in your country under your management as my partner, My name is Aisha Gaddafi and presently living in Oman, i am a Widow and single Mother with three Children, the only biological Daughter of late Libyan President (Late Colonel Muammar Gaddafi) and presently i am under political asylum protection by the Omani Government. I have funds worth"Twenty Seven Million Five Hundred Thousand United State Dollars" $27.500.000.00 US Dollar which i want to entrust on you for investment project in your country.If you are willing to handle this project on my behalf, kindly reply urgent to enable me provide you more details to start the transfer process. I shall appreciate your urgent response through my email address. Best Regards Mrs Aisha Gaddaf
Re: [PATCH] powerpc/5200: update contact email
On Sat, 2 May 2020 16:26:42 +0200, Wolfram Sang wrote: > My 'pengutronix' address is defunct for years. Merge the entries and use > the proper contact address. Applied to powerpc/next. [1/1] powerpc/5200: update contact email https://git.kernel.org/powerpc/c/ad0f522df1b2f4fe5d4ae6418e1ea216154a0662 cheers
Re: [PATCH] i2c: algo-pca: update contact email
On Sat, May 02, 2020 at 04:26:49PM +0200, Wolfram Sang wrote: > The 'pengutronix' address is defunct for years. Use the proper contact > address. > > Signed-off-by: Wolfram Sang Applied to for-current, thanks! signature.asc Description: PGP signature
Re: [PATCH] rtc: stmp3xxx: update contact email
On 02/05/2020 16:27:04+0200, Wolfram Sang wrote: > The 'pengutronix' address is defunct for years. Use the proper contact > address. > > Signed-off-by: Wolfram Sang > --- > drivers/rtc/rtc-stmp3xxx.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > Applied, thanks. -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Re: linux-next: new contact(s) for the ceph tree?
Hi Ilya,
On Sun, 10 May 2020 09:40:07 +0200 Ilya Dryomov wrote:
>
> On Sat, May 9, 2020 at 5:47 AM Stephen Rothwell wrote:
> >
> > On Sat, 9 May 2020 01:03:14 + (UTC) Sage Weil
> > wrote:
> > >
> > > Jeff Layton
> >
> > Done.
> > > On Sat, 9 May 2020, Stephen Rothwell wrote:
> > > >
> > > > I noticed commit
> > > >
> > > > 3a5ccecd9af7 ("MAINTAINERS: remove myself as ceph co-maintainer")
> > > >
> > > > appear recently. So who should I now list as the contact(s) for the
> > > > ceph tree?
>
> I thought maintainers were on the list automatically. If there is
> a separate list, please add me as well.
Done.
--
Cheers,
Stephen Rothwell
pgphSym61DfqW.pgp
Description: OpenPGP digital signature
Re: linux-next: new contact(s) for the ceph tree?
On Sat, May 9, 2020 at 5:47 AM Stephen Rothwell wrote:
>
> Hi Sage,
>
> On Sat, 9 May 2020 01:03:14 + (UTC) Sage Weil wrote:
> >
> > Jeff Layton
>
> Done.
> > On Sat, 9 May 2020, Stephen Rothwell wrote:
> > >
> > > I noticed commit
> > >
> > > 3a5ccecd9af7 ("MAINTAINERS: remove myself as ceph co-maintainer")
> > >
> > > appear recently. So who should I now list as the contact(s) for the
> > > ceph tree?
Hi Stephen,
I thought maintainers were on the list automatically. If there is
a separate list, please add me as well.
Thanks,
Ilya
Re: linux-next: new contact(s) for the ceph tree?
Hi Sage,
On Sat, 9 May 2020 01:03:14 + (UTC) Sage Weil wrote:
>
> Jeff Layton
Done.
> On Sat, 9 May 2020, Stephen Rothwell wrote:
> >
> > I noticed commit
> >
> > 3a5ccecd9af7 ("MAINTAINERS: remove myself as ceph co-maintainer")
> >
> > appear recently. So who should I now list as the contact(s) for the
> > ceph tree?
--
Cheers,
Stephen Rothwell
pgpFBm3Lw0tD_.pgp
Description: OpenPGP digital signature
Re: linux-next: new contact(s) for the ceph tree?
Jeff Layton
Thanks, Stephen!
sage
On Sat, 9 May 2020, Stephen Rothwell wrote:
> Hi all,
>
> I noticed commit
>
> 3a5ccecd9af7 ("MAINTAINERS: remove myself as ceph co-maintainer")
>
> appear recently. So who should I now list as the contact(s) for the
> ceph tree?
>
> --
> Cheers,
> Stephen Rothwell
>
linux-next: new contact(s) for the ceph tree?
Hi all,
I noticed commit
3a5ccecd9af7 ("MAINTAINERS: remove myself as ceph co-maintainer")
appear recently. So who should I now list as the contact(s) for the
ceph tree?
--
Cheers,
Stephen Rothwell
pgpexj9wNPTSv.pgp
Description: OpenPGP digital signature
Re: [PATCH] mmc: sdhci-esdhc: update contact email
On Sat, 2 May 2020 at 16:28, Wolfram Sang wrote: > > The 'pengutronix' address is defunct for years. Use the proper contact > address. > > Signed-off-by: Wolfram Sang Applied for next, thanks! Kind regards Uffe > --- > drivers/mmc/host/sdhci-esdhc.h | 2 +- > include/linux/platform_data/mmc-esdhc-imx.h | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/mmc/host/sdhci-esdhc.h b/drivers/mmc/host/sdhci-esdhc.h > index 947212f16bc6..a30796e79b1c 100644 > --- a/drivers/mmc/host/sdhci-esdhc.h > +++ b/drivers/mmc/host/sdhci-esdhc.h > @@ -5,7 +5,7 @@ > * Copyright (c) 2007 Freescale Semiconductor, Inc. > * Copyright (c) 2009 MontaVista Software, Inc. > * Copyright (c) 2010 Pengutronix e.K. > - * Author: Wolfram Sang > + * Author: Wolfram Sang > */ > > #ifndef _DRIVERS_MMC_SDHCI_ESDHC_H > diff --git a/include/linux/platform_data/mmc-esdhc-imx.h > b/include/linux/platform_data/mmc-esdhc-imx.h > index 0434f68eda86..cba1184b364c 100644 > --- a/include/linux/platform_data/mmc-esdhc-imx.h > +++ b/include/linux/platform_data/mmc-esdhc-imx.h > @@ -1,6 +1,6 @@ > /* SPDX-License-Identifier: GPL-2.0-only */ > /* > - * Copyright 2010 Wolfram Sang > + * Copyright 2010 Wolfram Sang > */ > > #ifndef __ASM_ARCH_IMX_ESDHC_H > -- > 2.20.1 >
Re: [PATCH] hwmon: adt7411: update contact email
On Sat, May 02, 2020 at 04:27:00PM +0200, Wolfram Sang wrote:
> My 'pengutronix' address is defunct for years. Merge the entries and use
> the proper contact address.
>
> Signed-off-by: Wolfram Sang
Applied.
Thanks,
Guenter
> ---
> drivers/hwmon/adt7411.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/hwmon/adt7411.c b/drivers/hwmon/adt7411.c
> index c7010b91bc13..5a839cc2ed1c 100644
> --- a/drivers/hwmon/adt7411.c
> +++ b/drivers/hwmon/adt7411.c
> @@ -716,7 +716,6 @@ static struct i2c_driver adt7411_driver = {
>
> module_i2c_driver(adt7411_driver);
>
> -MODULE_AUTHOR("Sascha Hauer and "
> - "Wolfram Sang ");
> +MODULE_AUTHOR("Sascha Hauer, Wolfram Sang ");
> MODULE_DESCRIPTION("ADT7411 driver");
> MODULE_LICENSE("GPL v2");
Re: [PATCH] powerpc/5200: update contact email
Wolfram Sang writes: >> > My 'pengutronix' address is defunct for years. Merge the entries and use >> > the proper contact address. >> >> Is there any point adding the new address? It's just likely to bit-rot >> one day too. > > At least, this one is a group address, not an individual one, so less > likey. > >> I figure the git history is a better source for more up-to-date emails. > > But yes, can still be argued. I won't persist if you don't like it. That's fine, I'll merge this. You've already gone to the trouble to send it and it's better than what we have now. cheers
Re: [PATCH] input: lm8333: update contact email
On Sat, May 02, 2020 at 04:26:39PM +0200, Wolfram Sang wrote: > The 'pengutronix' address is defunct for years. Use the proper contact > address. > > Signed-off-by: Wolfram Sang Applied, thank you. > --- > include/linux/input/lm8333.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/linux/input/lm8333.h b/include/linux/input/lm8333.h > index 79f918c6e8c5..906da5fc06e0 100644 > --- a/include/linux/input/lm8333.h > +++ b/include/linux/input/lm8333.h > @@ -1,6 +1,6 @@ > /* > * public include for LM8333 keypad driver - same license as driver > - * Copyright (C) 2012 Wolfram Sang, Pengutronix > + * Copyright (C) 2012 Wolfram Sang, Pengutronix > */ > > #ifndef _LM8333_H > -- > 2.20.1 > -- Dmitry
Re: [PATCH] powerpc/5200: update contact email
> > My 'pengutronix' address is defunct for years. Merge the entries and use > > the proper contact address. > > Is there any point adding the new address? It's just likely to bit-rot > one day too. At least, this one is a group address, not an individual one, so less likey. > I figure the git history is a better source for more up-to-date emails. But yes, can still be argued. I won't persist if you don't like it. Thanks! signature.asc Description: PGP signature
Re: [PATCH] ASoC: codecs: max9768: update contact email
On Sat, 2 May 2020 16:26:46 +0200, Wolfram Sang wrote: > The 'pengutronix' address is defunct for years. Use the proper contact > address. > > Signed-off-by: Wolfram Sang > --- > sound/soc/codecs/max9768.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.7 Thanks! [1/1] ASoC: codecs: max9768: update contact email commit: 454b3766de45f8508b343e509fdde959b4ff289c All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
Re: [PATCH] powerpc/5200: update contact email
Wolfram Sang writes: > My 'pengutronix' address is defunct for years. Merge the entries and use > the proper contact address. Is there any point adding the new address? It's just likely to bit-rot one day too. I figure the git history is a better source for more up-to-date emails. cheers > diff --git a/arch/powerpc/boot/dts/pcm032.dts > b/arch/powerpc/boot/dts/pcm032.dts > index c259c6b3ac5a..780e13d99e7b 100644 > --- a/arch/powerpc/boot/dts/pcm032.dts > +++ b/arch/powerpc/boot/dts/pcm032.dts > @@ -3,9 +3,7 @@ > * phyCORE-MPC5200B-IO (pcm032) board Device Tree Source > * > * Copyright (C) 2006-2009 Pengutronix > - * Sascha Hauer > - * Juergen Beisert > - * Wolfram Sang > + * Sascha Hauer, Juergen Beisert, Wolfram Sang > */ > > /include/ "mpc5200b.dtsi" > -- > 2.20.1
Re: [PATCH] mmc: sdhci-esdhc: update contact email
On 2/05/20 5:28 pm, Wolfram Sang wrote: > The 'pengutronix' address is defunct for years. Use the proper contact > address. > > Signed-off-by: Wolfram Sang Acked-by: Adrian Hunter > --- > drivers/mmc/host/sdhci-esdhc.h | 2 +- > include/linux/platform_data/mmc-esdhc-imx.h | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/mmc/host/sdhci-esdhc.h b/drivers/mmc/host/sdhci-esdhc.h > index 947212f16bc6..a30796e79b1c 100644 > --- a/drivers/mmc/host/sdhci-esdhc.h > +++ b/drivers/mmc/host/sdhci-esdhc.h > @@ -5,7 +5,7 @@ > * Copyright (c) 2007 Freescale Semiconductor, Inc. > * Copyright (c) 2009 MontaVista Software, Inc. > * Copyright (c) 2010 Pengutronix e.K. > - * Author: Wolfram Sang > + * Author: Wolfram Sang > */ > > #ifndef _DRIVERS_MMC_SDHCI_ESDHC_H > diff --git a/include/linux/platform_data/mmc-esdhc-imx.h > b/include/linux/platform_data/mmc-esdhc-imx.h > index 0434f68eda86..cba1184b364c 100644 > --- a/include/linux/platform_data/mmc-esdhc-imx.h > +++ b/include/linux/platform_data/mmc-esdhc-imx.h > @@ -1,6 +1,6 @@ > /* SPDX-License-Identifier: GPL-2.0-only */ > /* > - * Copyright 2010 Wolfram Sang > + * Copyright 2010 Wolfram Sang > */ > > #ifndef __ASM_ARCH_IMX_ESDHC_H >
Re: CONTACT MONEY GRAM FOR YOUR DAILY PAYMENT OF $5,000.00
-- Attention: Beneficiary, This is the second time we are notifying you about the statue of your compensation payment of ( $1,500,000.00). Be inform that We have been authorized by the United Nations Compensation Commission (UNCC) to release your compensation payment totaling the sum of US$1,500,000.00 through Money Gram transfer.You will be receiving the sum of $5,000.00 daily until the total sum of US $1,500,000.00 is completely transferred to you. Besides,we have already credited your first payment of US$5,000.00 today,therefore,you are advice to contact our director of foreign Remittance Department MR.ROBERT TAIWO and request him to give you the details of your first payment such as MoneyGram reference Numbers and senders name to enable you pick up your first payment of US$5,000.00 at any Money Gram office located around you.Kindly contact him through the information stated below for faster process. Contact Person: MR.ROBERT TAIWO E-MAIL: transfermoney...@foxmail.com Tel: (+229) 965 483 88 ( WhatsApp ) REMEMBER TO FORWARD HIM YOUR FULL INFORMATION AS REQUIRED BELOW TO ENABLE HIM LOCATE YOUR PAYMENT FILE AND ATTEND TO YOU IMMEDIATELY. 1. Your Full Name: 2. Address: 3. Age: 4. Occupation: 5. Telephone: 6. Country: NOTE: that the amount to be paid to you is (USD1.500, 000.00), we expect your urgent response to this email to enable us monitor the transaction effectively. Best Regards Mrs. Susan Dansuki.
Re: [PATCH] mmc: sdhci-esdhc: update contact email
On Sat, May 02, 2020 at 08:39:16AM -0700, Joe Perches wrote: > On Sat, 2020-05-02 at 16:28 +0200, Wolfram Sang wrote: > > The 'pengutronix' address is defunct for years. Use the proper contact > > address. > > Maybe add a .mailmap entry? Yes, it is in another patch: http://patchwork.ozlabs.org/project/linux-i2c/patch/20200502121840.9544-1-...@kernel.org/ Thanks! signature.asc Description: PGP signature
Re: [PATCH] mmc: sdhci-esdhc: update contact email
On Sat, 2020-05-02 at 16:28 +0200, Wolfram Sang wrote: > The 'pengutronix' address is defunct for years. Use the proper contact > address. Maybe add a .mailmap entry?
Re: [PATCH] watchdog: imx2_wdt: update contact email
On Sat, May 02, 2020 at 04:26:53PM +0200, Wolfram Sang wrote: > The 'pengutronix' address is defunct for years. Use the proper contact > address. > > Signed-off-by: Wolfram Sang Reviewed-by: Guenter Roeck > --- > drivers/watchdog/imx2_wdt.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/watchdog/imx2_wdt.c b/drivers/watchdog/imx2_wdt.c > index 1fe472f56cb3..b84f80f7d342 100644 > --- a/drivers/watchdog/imx2_wdt.c > +++ b/drivers/watchdog/imx2_wdt.c > @@ -2,7 +2,7 @@ > /* > * Watchdog driver for IMX2 and later processors > * > - * Copyright (C) 2010 Wolfram Sang, Pengutronix e.K. > + * Copyright (C) 2010 Wolfram Sang, Pengutronix e.K. > * Copyright (C) 2014 Freescale Semiconductor, Inc. > * > * some parts adapted by similar drivers from Darius Augulis and Vladimir > -- > 2.20.1 >
[PATCH] mmc: sdhci-esdhc: update contact email
The 'pengutronix' address is defunct for years. Use the proper contact address. Signed-off-by: Wolfram Sang --- drivers/mmc/host/sdhci-esdhc.h | 2 +- include/linux/platform_data/mmc-esdhc-imx.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/mmc/host/sdhci-esdhc.h b/drivers/mmc/host/sdhci-esdhc.h index 947212f16bc6..a30796e79b1c 100644 --- a/drivers/mmc/host/sdhci-esdhc.h +++ b/drivers/mmc/host/sdhci-esdhc.h @@ -5,7 +5,7 @@ * Copyright (c) 2007 Freescale Semiconductor, Inc. * Copyright (c) 2009 MontaVista Software, Inc. * Copyright (c) 2010 Pengutronix e.K. - * Author: Wolfram Sang + * Author: Wolfram Sang */ #ifndef _DRIVERS_MMC_SDHCI_ESDHC_H diff --git a/include/linux/platform_data/mmc-esdhc-imx.h b/include/linux/platform_data/mmc-esdhc-imx.h index 0434f68eda86..cba1184b364c 100644 --- a/include/linux/platform_data/mmc-esdhc-imx.h +++ b/include/linux/platform_data/mmc-esdhc-imx.h @@ -1,6 +1,6 @@ /* SPDX-License-Identifier: GPL-2.0-only */ /* - * Copyright 2010 Wolfram Sang + * Copyright 2010 Wolfram Sang */ #ifndef __ASM_ARCH_IMX_ESDHC_H -- 2.20.1
[PATCH] rtc: stmp3xxx: update contact email
The 'pengutronix' address is defunct for years. Use the proper contact
address.
Signed-off-by: Wolfram Sang
---
drivers/rtc/rtc-stmp3xxx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-stmp3xxx.c b/drivers/rtc/rtc-stmp3xxx.c
index ff6488be385f..c9bc3d4a1e66 100644
--- a/drivers/rtc/rtc-stmp3xxx.c
+++ b/drivers/rtc/rtc-stmp3xxx.c
@@ -416,5 +416,5 @@ module_platform_driver(stmp3xxx_rtcdrv);
MODULE_DESCRIPTION("STMP3xxx RTC Driver");
MODULE_AUTHOR("dmitry pervushin and "
- "Wolfram Sang ");
+ "Wolfram Sang ");
MODULE_LICENSE("GPL");
--
2.20.1
[PATCH] can: mscan: mpc5xxx_can: update contact email
The 'pengutronix' address is defunct for years. Use the proper contact address. Signed-off-by: Wolfram Sang --- drivers/net/can/mscan/mpc5xxx_can.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/can/mscan/mpc5xxx_can.c b/drivers/net/can/mscan/mpc5xxx_can.c index e4f4b5c9ebd6..e254e04ae257 100644 --- a/drivers/net/can/mscan/mpc5xxx_can.c +++ b/drivers/net/can/mscan/mpc5xxx_can.c @@ -5,7 +5,7 @@ * Copyright (C) 2004-2005 Andrey Volkov , * Varma Electronics Oy * Copyright (C) 2008-2009 Wolfgang Grandegger - * Copyright (C) 2009 Wolfram Sang, Pengutronix + * Copyright (C) 2009 Wolfram Sang, Pengutronix */ #include -- 2.20.1
[PATCH] hwmon: adt7411: update contact email
My 'pengutronix' address is defunct for years. Merge the entries and use
the proper contact address.
Signed-off-by: Wolfram Sang
---
drivers/hwmon/adt7411.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/hwmon/adt7411.c b/drivers/hwmon/adt7411.c
index c7010b91bc13..5a839cc2ed1c 100644
--- a/drivers/hwmon/adt7411.c
+++ b/drivers/hwmon/adt7411.c
@@ -716,7 +716,6 @@ static struct i2c_driver adt7411_driver = {
module_i2c_driver(adt7411_driver);
-MODULE_AUTHOR("Sascha Hauer and "
- "Wolfram Sang ");
+MODULE_AUTHOR("Sascha Hauer, Wolfram Sang ");
MODULE_DESCRIPTION("ADT7411 driver");
MODULE_LICENSE("GPL v2");
--
2.20.1
[PATCH] watchdog: imx2_wdt: update contact email
The 'pengutronix' address is defunct for years. Use the proper contact address. Signed-off-by: Wolfram Sang --- drivers/watchdog/imx2_wdt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/watchdog/imx2_wdt.c b/drivers/watchdog/imx2_wdt.c index 1fe472f56cb3..b84f80f7d342 100644 --- a/drivers/watchdog/imx2_wdt.c +++ b/drivers/watchdog/imx2_wdt.c @@ -2,7 +2,7 @@ /* * Watchdog driver for IMX2 and later processors * - * Copyright (C) 2010 Wolfram Sang, Pengutronix e.K. + * Copyright (C) 2010 Wolfram Sang, Pengutronix e.K. * Copyright (C) 2014 Freescale Semiconductor, Inc. * * some parts adapted by similar drivers from Darius Augulis and Vladimir -- 2.20.1
[PATCH] i2c: algo-pca: update contact email
The 'pengutronix' address is defunct for years. Use the proper contact
address.
Signed-off-by: Wolfram Sang
---
drivers/i2c/algos/i2c-algo-pca.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/algos/i2c-algo-pca.c b/drivers/i2c/algos/i2c-algo-pca.c
index dff4e178c732..7f10312d1b88 100644
--- a/drivers/i2c/algos/i2c-algo-pca.c
+++ b/drivers/i2c/algos/i2c-algo-pca.c
@@ -542,7 +542,7 @@ int i2c_pca_add_numbered_bus(struct i2c_adapter *adap)
EXPORT_SYMBOL(i2c_pca_add_numbered_bus);
MODULE_AUTHOR("Ian Campbell , "
- "Wolfram Sang ");
+ "Wolfram Sang ");
MODULE_DESCRIPTION("I2C-Bus PCA9564/PCA9665 algorithm");
MODULE_LICENSE("GPL");
--
2.20.1
[PATCH] powerpc/5200: update contact email
My 'pengutronix' address is defunct for years. Merge the entries and use the proper contact address. Signed-off-by: Wolfram Sang --- arch/powerpc/boot/dts/pcm032.dts | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/arch/powerpc/boot/dts/pcm032.dts b/arch/powerpc/boot/dts/pcm032.dts index c259c6b3ac5a..780e13d99e7b 100644 --- a/arch/powerpc/boot/dts/pcm032.dts +++ b/arch/powerpc/boot/dts/pcm032.dts @@ -3,9 +3,7 @@ * phyCORE-MPC5200B-IO (pcm032) board Device Tree Source * * Copyright (C) 2006-2009 Pengutronix - * Sascha Hauer - * Juergen Beisert - * Wolfram Sang + * Sascha Hauer, Juergen Beisert, Wolfram Sang */ /include/ "mpc5200b.dtsi" -- 2.20.1
[PATCH] input: lm8333: update contact email
The 'pengutronix' address is defunct for years. Use the proper contact address. Signed-off-by: Wolfram Sang --- include/linux/input/lm8333.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/input/lm8333.h b/include/linux/input/lm8333.h index 79f918c6e8c5..906da5fc06e0 100644 --- a/include/linux/input/lm8333.h +++ b/include/linux/input/lm8333.h @@ -1,6 +1,6 @@ /* * public include for LM8333 keypad driver - same license as driver - * Copyright (C) 2012 Wolfram Sang, Pengutronix + * Copyright (C) 2012 Wolfram Sang, Pengutronix */ #ifndef _LM8333_H -- 2.20.1
[PATCH] ASoC: codecs: max9768: update contact email
The 'pengutronix' address is defunct for years. Use the proper contact
address.
Signed-off-by: Wolfram Sang
---
sound/soc/codecs/max9768.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/codecs/max9768.c b/sound/soc/codecs/max9768.c
index d0737db5868a..39dda1b03b3d 100644
--- a/sound/soc/codecs/max9768.c
+++ b/sound/soc/codecs/max9768.c
@@ -220,6 +220,6 @@ static struct i2c_driver max9768_i2c_driver = {
};
module_i2c_driver(max9768_i2c_driver);
-MODULE_AUTHOR("Wolfram Sang ");
+MODULE_AUTHOR("Wolfram Sang ");
MODULE_DESCRIPTION("ASoC MAX9768 amplifier driver");
MODULE_LICENSE("GPL v2");
--
2.20.1
Re: [PATCH] Documentation/process: Add Google contact for embargoed hardware issues
On Wed, Sep 04, 2019 at 09:24:49AM -0700, Kees Cook wrote: > This adds myself as the Google contact for embargoed hardware security > issues and fixes some small typos. > > Cc: Guenter Roeck > Cc: Matt Linton > Cc: Matthew Garrett > Signed-off-by: Kees Cook Acked-by: Guenter Roeck > --- > Documentation/process/embargoed-hardware-issues.rst | 8 > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/Documentation/process/embargoed-hardware-issues.rst > b/Documentation/process/embargoed-hardware-issues.rst > index d37cbc502936..1c1ad684d753 100644 > --- a/Documentation/process/embargoed-hardware-issues.rst > +++ b/Documentation/process/embargoed-hardware-issues.rst > @@ -5,7 +5,7 @@ Scope > - > > Hardware issues which result in security problems are a different category > -of security bugs than pure software bugs which only affect the Linux > +of security bugs than pure software bugs which only affect the Linux > kernel. > > Hardware issues like Meltdown, Spectre, L1TF etc. must be treated > @@ -159,7 +159,7 @@ Mitigation development > > The initial response team sets up an encrypted mailing-list or repurposes > an existing one if appropriate. The disclosing party should provide a list > -of contacts for all other parties who have already been, or should be > +of contacts for all other parties who have already been, or should be, > informed about the issue. The response team contacts these parties so they > can name experts who should be subscribed to the mailing-list. > > @@ -230,8 +230,8 @@ an involved disclosed party. The current ambassadors list: >SUSE Jiri Kosina > >Amazon > - Google > - == > + Google Kees Cook > + = ======== > > If you want your organization to be added to the ambassadors list, please > contact the hardware security team. The nominated ambassador has to > -- > 2.17.1 > > > -- > Kees Cook
[PATCH] Documentation/process: Add Google contact for embargoed hardware issues
This adds myself as the Google contact for embargoed hardware security issues and fixes some small typos. Cc: Guenter Roeck Cc: Matt Linton Cc: Matthew Garrett Signed-off-by: Kees Cook --- Documentation/process/embargoed-hardware-issues.rst | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst index d37cbc502936..1c1ad684d753 100644 --- a/Documentation/process/embargoed-hardware-issues.rst +++ b/Documentation/process/embargoed-hardware-issues.rst @@ -5,7 +5,7 @@ Scope - Hardware issues which result in security problems are a different category -of security bugs than pure software bugs which only affect the Linux +of security bugs than pure software bugs which only affect the Linux kernel. Hardware issues like Meltdown, Spectre, L1TF etc. must be treated @@ -159,7 +159,7 @@ Mitigation development The initial response team sets up an encrypted mailing-list or repurposes an existing one if appropriate. The disclosing party should provide a list -of contacts for all other parties who have already been, or should be +of contacts for all other parties who have already been, or should be, informed about the issue. The response team contacts these parties so they can name experts who should be subscribed to the mailing-list. @@ -230,8 +230,8 @@ an involved disclosed party. The current ambassadors list: SUSE Jiri Kosina Amazon - Google - == + Google Kees Cook + = If you want your organization to be added to the ambassadors list, please contact the hardware security team. The nominated ambassador has to -- 2.17.1 -- Kees Cook
Dear Greetings to you Contact my secretary immediately From Dr Frederic, Your Compensation
Dear Greetings to you Contact my secretary immediately From Dr Frederic, Your Compensation for your past efforts Compliments of the day and God's blessings. I am glad to inform you that I have successfully completed the transaction. The money has been transferred to Switzerland. I succeeded through the assistance of my new business partner from the United States of America. Currently I am in India with him for a business trip. However, I did not forget your past efforts in helping me then though you weren't able to complete the project with me but honestly, I still appreciate your past efforts. In appreciation towards your assistance, we jointly mapped out the sum of (US$900,000.00) and wrote in your favour a certified bank cheque, payable to your account only which was left with my secretary and you are expected to contact her immediately and negotiate with her the best way to send it to you. Contact my secretary immediately you receive this mail at her contact information below and negotiate with her the best and safest way you want her to send the bank draft to you. Name: Mrs. Joy Max, Call +229 66836241, Email Address: mrsjoymax...@outlook.fr, Once again, thank you very much and remain blessed with your family.Let me know as soon as you receive your bank draft. Best Regards, Dr Frederic H Koute,
[PATCH 4.14 42/45] HID: wacom: Send BTN_TOUCH in response to INTUOSP2_BT eraser contact
From: Jason Gerecke
commit fe7f8d73d1af19b678171170e4e5384deb57833d upstream.
The Bluetooth reports from the 2nd-gen Intuos Pro have separate bits for
indicating if the tip or eraser is in contact with the tablet. At the
moment, only the tip contact bit controls the state of the BTN_TOUCH
event. This prevents the eraser from working as expected. This commit
changes the driver to send BTN_TOUCH whenever either the tip or eraser
contact bit is set.
Fixes: 4922cd26f03c ("HID: wacom: Support 2nd-gen Intuos Pro's Bluetooth
classic interface")
Cc: # 4.11+
Signed-off-by: Jason Gerecke
Reviewed-by: Aaron Skomra
Signed-off-by: Benjamin Tissoires
Signed-off-by: Greg Kroah-Hartman
---
drivers/hid/wacom_wac.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/hid/wacom_wac.c
+++ b/drivers/hid/wacom_wac.c
@@ -1275,7 +1275,7 @@ static void wacom_intuos_pro2_bt_pen(str
input_report_abs(pen_input, ABS_PRESSURE,
get_unaligned_le16([5]));
input_report_abs(pen_input, ABS_DISTANCE, range ?
frame[13] : wacom->features.distance_max);
- input_report_key(pen_input, BTN_TOUCH, frame[0] & 0x01);
+ input_report_key(pen_input, BTN_TOUCH, frame[0] & 0x09);
input_report_key(pen_input, BTN_STYLUS, frame[0] &
0x02);
input_report_key(pen_input, BTN_STYLUS2, frame[0] &
0x04);
[PATCH 5.1 009/115] HID: wacom: Send BTN_TOUCH in response to INTUOSP2_BT eraser contact
From: Jason Gerecke
commit fe7f8d73d1af19b678171170e4e5384deb57833d upstream.
The Bluetooth reports from the 2nd-gen Intuos Pro have separate bits for
indicating if the tip or eraser is in contact with the tablet. At the
moment, only the tip contact bit controls the state of the BTN_TOUCH
event. This prevents the eraser from working as expected. This commit
changes the driver to send BTN_TOUCH whenever either the tip or eraser
contact bit is set.
Fixes: 4922cd26f03c ("HID: wacom: Support 2nd-gen Intuos Pro's Bluetooth
classic interface")
Cc: # 4.11+
Signed-off-by: Jason Gerecke
Reviewed-by: Aaron Skomra
Signed-off-by: Benjamin Tissoires
Signed-off-by: Greg Kroah-Hartman
---
drivers/hid/wacom_wac.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/hid/wacom_wac.c
+++ b/drivers/hid/wacom_wac.c
@@ -1301,7 +1301,7 @@ static void wacom_intuos_pro2_bt_pen(str
range ? frame[7] :
wacom->features.distance_max);
}
- input_report_key(pen_input, BTN_TOUCH, frame[0] & 0x01);
+ input_report_key(pen_input, BTN_TOUCH, frame[0] & 0x09);
input_report_key(pen_input, BTN_STYLUS, frame[0] &
0x02);
input_report_key(pen_input, BTN_STYLUS2, frame[0] &
0x04);
[PATCH 4.19 06/75] HID: wacom: Send BTN_TOUCH in response to INTUOSP2_BT eraser contact
From: Jason Gerecke
commit fe7f8d73d1af19b678171170e4e5384deb57833d upstream.
The Bluetooth reports from the 2nd-gen Intuos Pro have separate bits for
indicating if the tip or eraser is in contact with the tablet. At the
moment, only the tip contact bit controls the state of the BTN_TOUCH
event. This prevents the eraser from working as expected. This commit
changes the driver to send BTN_TOUCH whenever either the tip or eraser
contact bit is set.
Fixes: 4922cd26f03c ("HID: wacom: Support 2nd-gen Intuos Pro's Bluetooth
classic interface")
Cc: # 4.11+
Signed-off-by: Jason Gerecke
Reviewed-by: Aaron Skomra
Signed-off-by: Benjamin Tissoires
Signed-off-by: Greg Kroah-Hartman
---
drivers/hid/wacom_wac.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/hid/wacom_wac.c
+++ b/drivers/hid/wacom_wac.c
@@ -1299,7 +1299,7 @@ static void wacom_intuos_pro2_bt_pen(str
range ? frame[7] :
wacom->features.distance_max);
}
- input_report_key(pen_input, BTN_TOUCH, frame[0] & 0x01);
+ input_report_key(pen_input, BTN_TOUCH, frame[0] & 0x09);
input_report_key(pen_input, BTN_STYLUS, frame[0] &
0x02);
input_report_key(pen_input, BTN_STYLUS2, frame[0] &
0x04);
Decision makers contact list
Hi, Would you be interested in targeting Cybersecurity Users across the globe for your Q1 marketing strategy? Here is how we can help you: Security users by vendor: Cisco, Juniper, Check Point, Aruba Networks, Symantec and many others. Security users by security solution: Email, SIEM, Firewall, UTM, Endpoint, DDoS, IAM, Cloud security, App security, Web security, Vulnerability, VPN, Authentication and many others. Cloud users of IaaS, PaaS and SaaS: AWS, Azure, Rackspace, vCloud, Salesforce, Jira, ServiceNow, SharePoint, Office 365, Box, Workday, SuccessFactors and many others. For Channel and Partner: MSP, MSSP and CSP companies decision makers, Industry specific IT security decision makers Banks, Credit unions, Insurance, Education, Healthcare, Retail, Manufacturing, Government, Oil and Gas and many others. We can customize this list as per your specific technology, revenue size of companies and job titles from those companies. Await for your positive response! Thanks, Martha Evans If not, I would be happy to update my notes I just need to hear from you first!
Your OHA contact form
WilliamslupE: Thank you for filling out our online contact form. Onondaga Historical Association
CONTACT PAYMENT COORDINATOR
-- Dear customer, As part of annual program of IMF in the fight against global poverty, we wish to inform you that you are a beneficiary of $1 Million. To receive your Visa card, contact: i...@visatmonline.com Thanks Ann
Contact Him.
Attn:The Beneficiary Under the United Nations scam victims rehabilitation scheme You are listed and approved to receive payment of of US$750.000.00 as one of the scammed victims. Be guided therefore to get in touch with the country supervising payment officer in Nigeria ASAP via his given information so that he can release your funds to you as per our standing instruction. Name:- Mr.Paul Jones Email:- un-n...@live.com Notify us in writing as soon as you get paid of the above amount. Faithfully yours, Mrs.Josephine Morgan
E-mail Contact.
Hello, have you study the project proposal i sent you? --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
E-mail Contact.
Hello, have you study the project proposal i sent you? --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
CONTACT HIM NOW
Attn: My Dear I am glad to inform you that i have successfully concluded the transaction which i seek for your family help before, Now the fund has been transferred to Hong Kong through the assistant of Mr.Wong Lee, who is a business man base in Hong Kong.Once again, I have mapped out a compensation fund and wrote on your favor a certified bank draft $2.5Million; I left the bank draft with a shipping office on my departure to Hong Kong.Kindly contact Hilla Ager, with below information and instruct Hilla Ager where to deliver the certified bank draft to you. Name: Hilla Ager Email: hill_...@yahoo.dk As soon as you receive the certified bank draft, you should let me know because i am busy here trying to put things together and may not be chanced to email you frequently,feel free to contact Hilla Ager, for the certified bank draft. Thanks and remain blessed. Mr. Larry Johnson
CONTACT HIM NOW
Attn: My Dear I am glad to inform you that i have successfully concluded the transaction which i seek for your family help before, Now the fund has been transferred to Hong Kong through the assistant of Mr.Wong Lee, who is a business man base in Hong Kong.Once again, I have mapped out a compensation fund and wrote on your favor a certified bank draft $2.5Million; I left the bank draft with a shipping office on my departure to Hong Kong.Kindly contact Hilla Ager, with below information and instruct Hilla Ager where to deliver the certified bank draft to you. Name: Hilla Ager Email: hill_...@yahoo.dk As soon as you receive the certified bank draft, you should let me know because i am busy here trying to put things together and may not be chanced to email you frequently,feel free to contact Hilla Ager, for the certified bank draft. Thanks and remain blessed. Mr. Larry Johnson
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sun, Oct 21, 2018 at 04:27:57AM -0400, Theodore Y. Ts'o wrote: > On Sat, Oct 20, 2018 at 03:14:20PM -0400, jonsm...@gmail.com wrote: > > > > Which is why the lawyers need to go over this document and I haven't > > seen anything posted from them. In the same vein Mauro is concerned > > that the way this is code is written it is a binding contract in > > Brazil. > > My understanding is that lawyers from the Linux Foundation have gone > over both the CoC and as well as the changes in this patchset, and > that this happened before they were sent out. That is correct.
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sun, Oct 21, 2018 at 04:27:57AM -0400, Theodore Y. Ts'o wrote: > On Sat, Oct 20, 2018 at 03:14:20PM -0400, jonsm...@gmail.com wrote: > > > > Which is why the lawyers need to go over this document and I haven't > > seen anything posted from them. In the same vein Mauro is concerned > > that the way this is code is written it is a binding contract in > > Brazil. > > My understanding is that lawyers from the Linux Foundation have gone > over both the CoC and as well as the changes in this patchset, and > that this happened before they were sent out. That is correct.
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sat, Oct 20, 2018 at 03:14:20PM -0400, jonsm...@gmail.com wrote: > > Which is why the lawyers need to go over this document and I haven't > seen anything posted from them. In the same vein Mauro is concerned > that the way this is code is written it is a binding contract in > Brazil. My understanding is that lawyers from the Linux Foundation have gone over both the CoC and as well as the changes in this patchset, and that this happened before they were sent out. - Ted
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sat, Oct 20, 2018 at 03:14:20PM -0400, jonsm...@gmail.com wrote: > > Which is why the lawyers need to go over this document and I haven't > seen anything posted from them. In the same vein Mauro is concerned > that the way this is code is written it is a binding contract in > Brazil. My understanding is that lawyers from the Linux Foundation have gone over both the CoC and as well as the changes in this patchset, and that this happened before they were sent out. - Ted
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sun, 21 Oct 2018, Alan Cox wrote: > > I don't see it specifically stating that 'If someone is offensive at a > kernel summit we are going to refuse to listen' Kernel summit or Maintainer summit is covered by the CoC of the conference it is attached to. Thanks, tglx
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sun, 21 Oct 2018, Alan Cox wrote: > > I don't see it specifically stating that 'If someone is offensive at a > kernel summit we are going to refuse to listen' Kernel summit or Maintainer summit is covered by the CoC of the conference it is attached to. Thanks, tglx
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
> > Data protection law, reporting laws in some > > countries and the like mean that anyone expecting an incident to remain > > confidential from the person it was reported against is living in > > dreamland and are going to get a nasty shock. > > OK - you seem to be talking about keeping the incident and reporter > confidential from the person reported against. > Certainly the person reported against has to have the incident > identified to them, so that part is not confidential. Many legal > jurisdictions require that the accused can know their accuser. > But these things come into play mostly when items have veered > into legal territory. Most violation reports are not in the territory. > There's no legal requirement that the Code of Conduct committee > tell someone who it was that said they were rude on the mailing list. The 'who said' is generally safe (except from the it's in court case - which is fine when that happens the legal process deals with it). The other details are not so while someone accused of something might not know who said it they can ask for what personal data (which would include that email with names etc scrubbed). You can possibly fight that in court of course, if you've got lots of money and nothing better to do for six weeks. > > You should also reserving the right to report serious incidents directly > > to law enforcement. Unless of course you want to be forced to sit on > > multiple reports of physical abuse from different people about > > someone - unable to tell them about each others report, unable to prove > > anything, and in twenty years time having to explain to the media why > > nothing was done. > > The scope of the code of conduct basically means that it covers > online interactions (communication via mailing list, git commits > and Bugzilla). I don't see it specifically stating that 'If someone is offensive at a kernel summit we are going to refuse to listen' Seriously ? Alan
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
> > Data protection law, reporting laws in some > > countries and the like mean that anyone expecting an incident to remain > > confidential from the person it was reported against is living in > > dreamland and are going to get a nasty shock. > > OK - you seem to be talking about keeping the incident and reporter > confidential from the person reported against. > Certainly the person reported against has to have the incident > identified to them, so that part is not confidential. Many legal > jurisdictions require that the accused can know their accuser. > But these things come into play mostly when items have veered > into legal territory. Most violation reports are not in the territory. > There's no legal requirement that the Code of Conduct committee > tell someone who it was that said they were rude on the mailing list. The 'who said' is generally safe (except from the it's in court case - which is fine when that happens the legal process deals with it). The other details are not so while someone accused of something might not know who said it they can ask for what personal data (which would include that email with names etc scrubbed). You can possibly fight that in court of course, if you've got lots of money and nothing better to do for six weeks. > > You should also reserving the right to report serious incidents directly > > to law enforcement. Unless of course you want to be forced to sit on > > multiple reports of physical abuse from different people about > > someone - unable to tell them about each others report, unable to prove > > anything, and in twenty years time having to explain to the media why > > nothing was done. > > The scope of the code of conduct basically means that it covers > online interactions (communication via mailing list, git commits > and Bugzilla). I don't see it specifically stating that 'If someone is offensive at a kernel summit we are going to refuse to listen' Seriously ? Alan
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sat, 2018-10-20 at 19:28 +0100, Alan Cox wrote: > > +to the circumstances. The Code of Conduct Committee is obligated > > to > > +maintain confidentiality with regard to the reporter of an > > incident. > > +Further details of specific enforcement policies may be posted > > +separately. > > Unfortunately by ignoring the other suggestions on this you've left > this bit broken. > > The committee can't keep most stuff confidential so it's misleading > and wrong to imply they can. Data protection law, reporting laws in > some countries and the like mean that anyone expecting an incident to > remain confidential from the person it was reported against is living > in dreamland and are going to get a nasty shock. > > At the very least it should say '(except where required by law)'. I've got a solution for this: the patches I've been curating also modify the section so the merger will look like what I have below. The intent of the series I'm curating was only the beginning to show desire to change in 4.19 but to correct the obvious defect before we started the debate, so after suitable discussion, this one can be the final set. > There is a separate issue that serious things should always go to law > enforcement - you are setting up a policy akin to the one that got > the catholic church and many others in trouble. > > You should also reserving the right to report serious incidents > directly to law enforcement. Unless of course you want to be forced > to sit on multiple reports of physical abuse from different people > about someone - unable to tell them about each others report, unable > to prove anything, and in twenty years time having to explain to the > media why nothing was done. I think we should debate that. Most legal systems provide significant deference to victims wishing for confidentiality and we should both respect that and remember that an automatic crime report is a significant deterrent to vulnerable people in a lot of places. James --- diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst index eec768471a4d..8913851dab89 100644 --- a/Documentation/process/code-of-conduct.rst +++ b/Documentation/process/code-of-conduct.rst @@ -59,19 +59,27 @@ address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. -Reporting -= +Enforcement +=== Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported by contacting the Technical Advisory Board (TAB) at -. All complaints will be reviewed and -investigated and will result in a response that is deemed necessary and -appropriate to the circumstances. The TAB is obligated to maintain -confidentiality with regard to the reporter of an incident (except where -required by law). +reported by contacting the Code of Conduct Committee at +. All complaints will be reviewed and investigated +and will result in a response that is deemed necessary and appropriate +to the circumstances. The Code of Conduct Committee is obligated to +maintain confidentiality with regard to the reporter of an incident +(except where required by law). Further details of specific enforcement +policies may be posted separately. + Attribution === This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html + +Interpretation +== + +See the :ref:`code_of_conduct_interpretation` document for how the Linux +kernel community will be interpreting this document.
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sat, 2018-10-20 at 19:28 +0100, Alan Cox wrote: > > +to the circumstances. The Code of Conduct Committee is obligated > > to > > +maintain confidentiality with regard to the reporter of an > > incident. > > +Further details of specific enforcement policies may be posted > > +separately. > > Unfortunately by ignoring the other suggestions on this you've left > this bit broken. > > The committee can't keep most stuff confidential so it's misleading > and wrong to imply they can. Data protection law, reporting laws in > some countries and the like mean that anyone expecting an incident to > remain confidential from the person it was reported against is living > in dreamland and are going to get a nasty shock. > > At the very least it should say '(except where required by law)'. I've got a solution for this: the patches I've been curating also modify the section so the merger will look like what I have below. The intent of the series I'm curating was only the beginning to show desire to change in 4.19 but to correct the obvious defect before we started the debate, so after suitable discussion, this one can be the final set. > There is a separate issue that serious things should always go to law > enforcement - you are setting up a policy akin to the one that got > the catholic church and many others in trouble. > > You should also reserving the right to report serious incidents > directly to law enforcement. Unless of course you want to be forced > to sit on multiple reports of physical abuse from different people > about someone - unable to tell them about each others report, unable > to prove anything, and in twenty years time having to explain to the > media why nothing was done. I think we should debate that. Most legal systems provide significant deference to victims wishing for confidentiality and we should both respect that and remember that an automatic crime report is a significant deterrent to vulnerable people in a lot of places. James --- diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst index eec768471a4d..8913851dab89 100644 --- a/Documentation/process/code-of-conduct.rst +++ b/Documentation/process/code-of-conduct.rst @@ -59,19 +59,27 @@ address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. -Reporting -= +Enforcement +=== Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported by contacting the Technical Advisory Board (TAB) at -. All complaints will be reviewed and -investigated and will result in a response that is deemed necessary and -appropriate to the circumstances. The TAB is obligated to maintain -confidentiality with regard to the reporter of an incident (except where -required by law). +reported by contacting the Code of Conduct Committee at +. All complaints will be reviewed and investigated +and will result in a response that is deemed necessary and appropriate +to the circumstances. The Code of Conduct Committee is obligated to +maintain confidentiality with regard to the reporter of an incident +(except where required by law). Further details of specific enforcement +policies may be posted separately. + Attribution === This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html + +Interpretation +== + +See the :ref:`code_of_conduct_interpretation` document for how the Linux +kernel community will be interpreting this document.
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sat, 2018-10-20 at 19:24 +, tim.b...@sony.com wrote: > The scope of the code of conduct basically means that it covers > online interactions (communication via mailing list, git commits > and Bugzilla). Not to be flippant, but those are hardly mediums > that are susceptible to executing physical abuse. Also, they are > all mediums that leave a persistent, public trail. So I don't think > the > comparison is very apt here. > -- Tim If that is the case, then why does this need to go into the Linux kernel in the first place? The mailing lists, the kernel.org git repository, and bugzilla presumably all have "terms of use" pages that could specify the expected behaviour very explicitly, and could specify how arbitration works as part of those terms of use (and if enforcement is required, then it could specify legal venues etc). IOW: if the scope is just communication online, then I would think there are better tools for that. Putting a code of conduct into the kernel code itself wants to be justified by more than just regulating online behaviour. -- Trond Myklebust Linux NFS client maintainer, Hammerspace trond.mykleb...@hammerspace.com
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sat, 2018-10-20 at 19:24 +, tim.b...@sony.com wrote: > The scope of the code of conduct basically means that it covers > online interactions (communication via mailing list, git commits > and Bugzilla). Not to be flippant, but those are hardly mediums > that are susceptible to executing physical abuse. Also, they are > all mediums that leave a persistent, public trail. So I don't think > the > comparison is very apt here. > -- Tim If that is the case, then why does this need to go into the Linux kernel in the first place? The mailing lists, the kernel.org git repository, and bugzilla presumably all have "terms of use" pages that could specify the expected behaviour very explicitly, and could specify how arbitration works as part of those terms of use (and if enforcement is required, then it could specify legal venues etc). IOW: if the scope is just communication online, then I would think there are better tools for that. Putting a code of conduct into the kernel code itself wants to be justified by more than just regulating online behaviour. -- Trond Myklebust Linux NFS client maintainer, Hammerspace trond.mykleb...@hammerspace.com
RE: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
> -Original Message- > From: Alan Cox > > > +to the circumstances. The Code of Conduct Committee is obligated to > > +maintain confidentiality with regard to the reporter of an incident. > > +Further details of specific enforcement policies may be posted > > +separately. > > Unfortunately by ignoring the other suggestions on this you've left this > bit broken. > > The committee can't keep most stuff confidential so it's misleading and > wrong to imply they can. I disagree with this assessment. We have managed to keep most stuff confidential to the general public in the past, to the point where it has been argued that the TAB have not been transparent enough. We're trying to address that issue with the section about quarterly anonymized reports. > Data protection law, reporting laws in some > countries and the like mean that anyone expecting an incident to remain > confidential from the person it was reported against is living in > dreamland and are going to get a nasty shock. OK - you seem to be talking about keeping the incident and reporter confidential from the person reported against. Certainly the person reported against has to have the incident identified to them, so that part is not confidential. Many legal jurisdictions require that the accused can know their accuser. But these things come into play mostly when items have veered into legal territory. Most violation reports are not in the territory. There's no legal requirement that the Code of Conduct committee tell someone who it was that said they were rude on the mailing list. > At the very least it should say '(except where required by law)'. That might be a good to add. It would be helpful, IMHO, to re-visit the patch that's been floating around and see if it can be added on top of this. > There is a separate issue that serious things should always go to law > enforcement - you are setting up a policy akin to the one that got the > catholic church and many others in trouble. > > You should also reserving the right to report serious incidents directly > to law enforcement. Unless of course you want to be forced to sit on > multiple reports of physical abuse from different people about > someone - unable to tell them about each others report, unable to prove > anything, and in twenty years time having to explain to the media why > nothing was done. The scope of the code of conduct basically means that it covers online interactions (communication via mailing list, git commits and Bugzilla). Not to be flippant, but those are hardly mediums that are susceptible to executing physical abuse. Also, they are all mediums that leave a persistent, public trail. So I don't think the comparison is very apt here. -- Tim
RE: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
> -Original Message- > From: Alan Cox > > > +to the circumstances. The Code of Conduct Committee is obligated to > > +maintain confidentiality with regard to the reporter of an incident. > > +Further details of specific enforcement policies may be posted > > +separately. > > Unfortunately by ignoring the other suggestions on this you've left this > bit broken. > > The committee can't keep most stuff confidential so it's misleading and > wrong to imply they can. I disagree with this assessment. We have managed to keep most stuff confidential to the general public in the past, to the point where it has been argued that the TAB have not been transparent enough. We're trying to address that issue with the section about quarterly anonymized reports. > Data protection law, reporting laws in some > countries and the like mean that anyone expecting an incident to remain > confidential from the person it was reported against is living in > dreamland and are going to get a nasty shock. OK - you seem to be talking about keeping the incident and reporter confidential from the person reported against. Certainly the person reported against has to have the incident identified to them, so that part is not confidential. Many legal jurisdictions require that the accused can know their accuser. But these things come into play mostly when items have veered into legal territory. Most violation reports are not in the territory. There's no legal requirement that the Code of Conduct committee tell someone who it was that said they were rude on the mailing list. > At the very least it should say '(except where required by law)'. That might be a good to add. It would be helpful, IMHO, to re-visit the patch that's been floating around and see if it can be added on top of this. > There is a separate issue that serious things should always go to law > enforcement - you are setting up a policy akin to the one that got the > catholic church and many others in trouble. > > You should also reserving the right to report serious incidents directly > to law enforcement. Unless of course you want to be forced to sit on > multiple reports of physical abuse from different people about > someone - unable to tell them about each others report, unable to prove > anything, and in twenty years time having to explain to the media why > nothing was done. The scope of the code of conduct basically means that it covers online interactions (communication via mailing list, git commits and Bugzilla). Not to be flippant, but those are hardly mediums that are susceptible to executing physical abuse. Also, they are all mediums that leave a persistent, public trail. So I don't think the comparison is very apt here. -- Tim
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sat, Oct 20, 2018 at 2:47 PM Trond Myklebust wrote: > > On Sat, 2018-10-20 at 19:28 +0100, Alan Cox wrote: > > > +to the circumstances. The Code of Conduct Committee is obligated > > > to > > > +maintain confidentiality with regard to the reporter of an > > > incident. > > > +Further details of specific enforcement policies may be posted > > > +separately. > > > > Unfortunately by ignoring the other suggestions on this you've left > > this > > bit broken. > > > > The committee can't keep most stuff confidential so it's misleading > > and > > wrong to imply they can. Data protection law, reporting laws in some > > countries and the like mean that anyone expecting an incident to > > remain > > confidential from the person it was reported against is living in > > dreamland and are going to get a nasty shock. > > > > At the very least it should say '(except where required by law)'. > > > > There is a separate issue that serious things should always go to law > > enforcement - you are setting up a policy akin to the one that got > > the > > catholic church and many others in trouble. > > > > You should also reserving the right to report serious incidents > > directly > > to law enforcement. Unless of course you want to be forced to sit on > > multiple reports of physical abuse from different people about > > someone - unable to tell them about each others report, unable to > > prove > > anything, and in twenty years time having to explain to the media why > > nothing was done. > > > > ...and then you get into questions about how this committee will > respond to queries from said law enforcement, and indeed to which legal > systems the committee will or will not report incidents. > > Why would we want to be going down the path of trying to handle reports > about "serious incidents" in the first place? That seems way out of > scope for a code of conduct arbitration scheme. Even attempting to > counsel people as to whether or not they should report incidents can > get you in trouble in many parts of the world. > Which is why the lawyers need to go over this document and I haven't seen anything posted from them. In the same vein Mauro is concerned that the way this is code is written it is a binding contract in Brazil. > -- > Trond Myklebust > Linux NFS client maintainer, Hammerspace > trond.mykleb...@hammerspace.com > > -- Jon Smirl jonsm...@gmail.com
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sat, Oct 20, 2018 at 2:47 PM Trond Myklebust wrote: > > On Sat, 2018-10-20 at 19:28 +0100, Alan Cox wrote: > > > +to the circumstances. The Code of Conduct Committee is obligated > > > to > > > +maintain confidentiality with regard to the reporter of an > > > incident. > > > +Further details of specific enforcement policies may be posted > > > +separately. > > > > Unfortunately by ignoring the other suggestions on this you've left > > this > > bit broken. > > > > The committee can't keep most stuff confidential so it's misleading > > and > > wrong to imply they can. Data protection law, reporting laws in some > > countries and the like mean that anyone expecting an incident to > > remain > > confidential from the person it was reported against is living in > > dreamland and are going to get a nasty shock. > > > > At the very least it should say '(except where required by law)'. > > > > There is a separate issue that serious things should always go to law > > enforcement - you are setting up a policy akin to the one that got > > the > > catholic church and many others in trouble. > > > > You should also reserving the right to report serious incidents > > directly > > to law enforcement. Unless of course you want to be forced to sit on > > multiple reports of physical abuse from different people about > > someone - unable to tell them about each others report, unable to > > prove > > anything, and in twenty years time having to explain to the media why > > nothing was done. > > > > ...and then you get into questions about how this committee will > respond to queries from said law enforcement, and indeed to which legal > systems the committee will or will not report incidents. > > Why would we want to be going down the path of trying to handle reports > about "serious incidents" in the first place? That seems way out of > scope for a code of conduct arbitration scheme. Even attempting to > counsel people as to whether or not they should report incidents can > get you in trouble in many parts of the world. > Which is why the lawyers need to go over this document and I haven't seen anything posted from them. In the same vein Mauro is concerned that the way this is code is written it is a binding contract in Brazil. > -- > Trond Myklebust > Linux NFS client maintainer, Hammerspace > trond.mykleb...@hammerspace.com > > -- Jon Smirl jonsm...@gmail.com
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sat, 2018-10-20 at 19:28 +0100, Alan Cox wrote: > > +to the circumstances. The Code of Conduct Committee is obligated > > to > > +maintain confidentiality with regard to the reporter of an > > incident. > > +Further details of specific enforcement policies may be posted > > +separately. > > Unfortunately by ignoring the other suggestions on this you've left > this > bit broken. > > The committee can't keep most stuff confidential so it's misleading > and > wrong to imply they can. Data protection law, reporting laws in some > countries and the like mean that anyone expecting an incident to > remain > confidential from the person it was reported against is living in > dreamland and are going to get a nasty shock. > > At the very least it should say '(except where required by law)'. > > There is a separate issue that serious things should always go to law > enforcement - you are setting up a policy akin to the one that got > the > catholic church and many others in trouble. > > You should also reserving the right to report serious incidents > directly > to law enforcement. Unless of course you want to be forced to sit on > multiple reports of physical abuse from different people about > someone - unable to tell them about each others report, unable to > prove > anything, and in twenty years time having to explain to the media why > nothing was done. > ...and then you get into questions about how this committee will respond to queries from said law enforcement, and indeed to which legal systems the committee will or will not report incidents. Why would we want to be going down the path of trying to handle reports about "serious incidents" in the first place? That seems way out of scope for a code of conduct arbitration scheme. Even attempting to counsel people as to whether or not they should report incidents can get you in trouble in many parts of the world. -- Trond Myklebust Linux NFS client maintainer, Hammerspace trond.mykleb...@hammerspace.com
Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
On Sat, 2018-10-20 at 19:28 +0100, Alan Cox wrote: > > +to the circumstances. The Code of Conduct Committee is obligated > > to > > +maintain confidentiality with regard to the reporter of an > > incident. > > +Further details of specific enforcement policies may be posted > > +separately. > > Unfortunately by ignoring the other suggestions on this you've left > this > bit broken. > > The committee can't keep most stuff confidential so it's misleading > and > wrong to imply they can. Data protection law, reporting laws in some > countries and the like mean that anyone expecting an incident to > remain > confidential from the person it was reported against is living in > dreamland and are going to get a nasty shock. > > At the very least it should say '(except where required by law)'. > > There is a separate issue that serious things should always go to law > enforcement - you are setting up a policy akin to the one that got > the > catholic church and many others in trouble. > > You should also reserving the right to report serious incidents > directly > to law enforcement. Unless of course you want to be forced to sit on > multiple reports of physical abuse from different people about > someone - unable to tell them about each others report, unable to > prove > anything, and in twenty years time having to explain to the media why > nothing was done. > ...and then you get into questions about how this committee will respond to queries from said law enforcement, and indeed to which legal systems the committee will or will not report incidents. Why would we want to be going down the path of trying to handle reports about "serious incidents" in the first place? That seems way out of scope for a code of conduct arbitration scheme. Even attempting to counsel people as to whether or not they should report incidents can get you in trouble in many parts of the world. -- Trond Myklebust Linux NFS client maintainer, Hammerspace trond.mykleb...@hammerspace.com
Re: [PATCH 6/7] Code of Conduct: Change the contact email address
> +to the circumstances. The Code of Conduct Committee is obligated to > +maintain confidentiality with regard to the reporter of an incident. > +Further details of specific enforcement policies may be posted > +separately. Unfortunately by ignoring the other suggestions on this you've left this bit broken. The committee can't keep most stuff confidential so it's misleading and wrong to imply they can. Data protection law, reporting laws in some countries and the like mean that anyone expecting an incident to remain confidential from the person it was reported against is living in dreamland and are going to get a nasty shock. At the very least it should say '(except where required by law)'. There is a separate issue that serious things should always go to law enforcement - you are setting up a policy akin to the one that got the catholic church and many others in trouble. You should also reserving the right to report serious incidents directly to law enforcement. Unless of course you want to be forced to sit on multiple reports of physical abuse from different people about someone - unable to tell them about each others report, unable to prove anything, and in twenty years time having to explain to the media why nothing was done. Alan
Re: [PATCH 6/7] Code of Conduct: Change the contact email address
> +to the circumstances. The Code of Conduct Committee is obligated to > +maintain confidentiality with regard to the reporter of an incident. > +Further details of specific enforcement policies may be posted > +separately. Unfortunately by ignoring the other suggestions on this you've left this bit broken. The committee can't keep most stuff confidential so it's misleading and wrong to imply they can. Data protection law, reporting laws in some countries and the like mean that anyone expecting an incident to remain confidential from the person it was reported against is living in dreamland and are going to get a nasty shock. At the very least it should say '(except where required by law)'. There is a separate issue that serious things should always go to law enforcement - you are setting up a policy akin to the one that got the catholic church and many others in trouble. You should also reserving the right to report serious incidents directly to law enforcement. Unless of course you want to be forced to sit on multiple reports of physical abuse from different people about someone - unable to tell them about each others report, unable to prove anything, and in twenty years time having to explain to the media why nothing was done. Alan
[PATCH 6/7] Code of Conduct: Change the contact email address
The contact point for the kernel's Code of Conduct should now be the Code of Conduct Committee, not the full TAB. Change the email address in the file to properly reflect this. Acked-by: Chris Mason Acked-by: Olof Johansson Acked-by: Theodore Ts'o Acked-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman --- Documentation/process/code-of-conduct.rst | 13 +++-- 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst index 3046664c929e..be50294aebd5 100644 --- a/Documentation/process/code-of-conduct.rst +++ b/Documentation/process/code-of-conduct.rst @@ -65,12 +65,13 @@ Enforcement === Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported by contacting the Technical Advisory Board (TAB) at -. All complaints will be reviewed and -investigated and will result in a response that is deemed necessary and -appropriate to the circumstances. The TAB is obligated to maintain -confidentiality with regard to the reporter of an incident. Further details of -specific enforcement policies may be posted separately. +reported by contacting the Code of Conduct Committee at +. All complaints will be reviewed and investigated +and will result in a response that is deemed necessary and appropriate +to the circumstances. The Code of Conduct Committee is obligated to +maintain confidentiality with regard to the reporter of an incident. +Further details of specific enforcement policies may be posted +separately. Attribution === -- 2.19.1
[PATCH 6/7] Code of Conduct: Change the contact email address
The contact point for the kernel's Code of Conduct should now be the Code of Conduct Committee, not the full TAB. Change the email address in the file to properly reflect this. Acked-by: Chris Mason Acked-by: Olof Johansson Acked-by: Theodore Ts'o Acked-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman --- Documentation/process/code-of-conduct.rst | 13 +++-- 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst index 3046664c929e..be50294aebd5 100644 --- a/Documentation/process/code-of-conduct.rst +++ b/Documentation/process/code-of-conduct.rst @@ -65,12 +65,13 @@ Enforcement === Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported by contacting the Technical Advisory Board (TAB) at -. All complaints will be reviewed and -investigated and will result in a response that is deemed necessary and -appropriate to the circumstances. The TAB is obligated to maintain -confidentiality with regard to the reporter of an incident. Further details of -specific enforcement policies may be posted separately. +reported by contacting the Code of Conduct Committee at +. All complaints will be reviewed and investigated +and will result in a response that is deemed necessary and appropriate +to the circumstances. The Code of Conduct Committee is obligated to +maintain confidentiality with regard to the reporter of an incident. +Further details of specific enforcement policies may be posted +separately. Attribution === -- 2.19.1
P/Contact
Dear Sir Please contact for detailed information of funds transfer based on your surname, Your prompt response will be highly appreciated. Kind Regards, Allen Yun B.Group manager contact id..
P/Contact
Dear Sir Please contact for detailed information of funds transfer based on your surname, Your prompt response will be highly appreciated. Kind Regards, Allen Yun B.Group manager contact id..
I have been trying to contact you
I have been trying to contact you
I have been trying to contact you
I have been trying to contact you
Contact me for more details
Hello, I am Mr. Emeka Ezela, the head of International remittance Department, United Bank for Africa (UBA) I have a business deal i would like to propose to you. If you are interested to know more, kindly contact me on my private emails (emekaez...@mail.com) for more details. Regards, Mr. Emeka Ezela
Contact me for more details
Hello, I am Mr. Emeka Ezela, the head of International remittance Department, United Bank for Africa (UBA) I have a business deal i would like to propose to you. If you are interested to know more, kindly contact me on my private emails (emekaez...@mail.com) for more details. Regards, Mr. Emeka Ezela
Contact my secretary in Burkina-Faso
Dear Friend, Good day, this is Mr. Henri Zongo, I'm happy to inform you about my success in getting the fund $29.6Million transferred under the co-operation of a new partner from Dubai, Presently I'm in Dubai for investment projects with my own share of the total sum. Meanwhile,I didn't forget your past efforts and attempts to assist me in transferring those funds despite that it failed us some how. Now contact my secretary in Burkina-Faso, his name is Mr. Leonard Kabore and his email address is (leonard_kab...@outlook.com) and ask him to send you VISA ATM CARD which has loaded the sum of USD$1,000,000.00 (One Million United States Dollars issued in your name by our Bank (BOA) headquarter, this is for your compensation for all the past efforts and attempts to assist me in this matter. Note, you will withdraw your money in an ATM MACHINE in any part of the world, but the maximum is ($5,000) Fifteen Thousand Us Dollars in three transactions per day. So feel free and get in touched with my secretary and instruct him where to send the VISA ATM CARD to you. Please do let me know immediately you receive the ATM CARD so that we can share the joy. Please my main reason to compensate you with this amount is for you to keep your mouth shut, do not allow anybody to know about this deal ever, let it to be sealed between us because I don't want to have any problem in the future please!. This is how we contributed for your compensation, I contributed $600,000 dollars out of my own share while my new partner contributed, $400,000 dollars to make the total of $1,000,000.00 USD,please let the deal be sealed ok! delete every message you received so far concerning this deal in your mailbox. In the moment, I am very busy here because of the investment projects which me and the new partner are having at hand, finally, remember that I had forwarded instruction to my secretary on your behalf to receive that VISA ATM CARD, so feel free to get in touch with him and he will help you to send it to your address. I will be traveling to Qatar this evening with my partner for an investment project. Regards, Mr. Henri Zongo. Contact my secretary in Burkina-Faso
Contact my secretary in Burkina-Faso
Dear Friend, Good day, this is Mr. Henri Zongo, I'm happy to inform you about my success in getting the fund $29.6Million transferred under the co-operation of a new partner from Dubai, Presently I'm in Dubai for investment projects with my own share of the total sum. Meanwhile,I didn't forget your past efforts and attempts to assist me in transferring those funds despite that it failed us some how. Now contact my secretary in Burkina-Faso, his name is Mr. Leonard Kabore and his email address is (leonard_kab...@outlook.com) and ask him to send you VISA ATM CARD which has loaded the sum of USD$1,000,000.00 (One Million United States Dollars issued in your name by our Bank (BOA) headquarter, this is for your compensation for all the past efforts and attempts to assist me in this matter. Note, you will withdraw your money in an ATM MACHINE in any part of the world, but the maximum is ($5,000) Fifteen Thousand Us Dollars in three transactions per day. So feel free and get in touched with my secretary and instruct him where to send the VISA ATM CARD to you. Please do let me know immediately you receive the ATM CARD so that we can share the joy. Please my main reason to compensate you with this amount is for you to keep your mouth shut, do not allow anybody to know about this deal ever, let it to be sealed between us because I don't want to have any problem in the future please!. This is how we contributed for your compensation, I contributed $600,000 dollars out of my own share while my new partner contributed, $400,000 dollars to make the total of $1,000,000.00 USD,please let the deal be sealed ok! delete every message you received so far concerning this deal in your mailbox. In the moment, I am very busy here because of the investment projects which me and the new partner are having at hand, finally, remember that I had forwarded instruction to my secretary on your behalf to receive that VISA ATM CARD, so feel free to get in touch with him and he will help you to send it to your address. I will be traveling to Qatar this evening with my partner for an investment project. Regards, Mr. Henri Zongo. Contact my secretary in Burkina-Faso
Contact my secretary in Burkina-Faso
Dear Friend, Good day, this is Mr. Henri Zongo, I'm happy to inform you about my success in getting the fund $29.6Million transferred under the co-operation of a new partner from Dubai, Presently I'm in Dubai for investment projects with my own share of the total sum. Meanwhile,I didn't forget your past efforts and attempts to assist me in transferring those funds despite that it failed us some how. Now contact my secretary in Burkina-Faso, his name is Mr. Leonard Kabore and his email address is (leonard_kab...@outlook.com) and ask him to send you VISA ATM CARD which has loaded the sum of USD$1,000,000.00 (One Million United States Dollars issued in your name by our Bank (BOA) headquarter, this is for your compensation for all the past efforts and attempts to assist me in this matter. Note, you will withdraw your money in an ATM MACHINE in any part of the world, but the maximum is ($5,000) Fifteen Thousand Us Dollars in three transactions per day. So feel free and get in touched with my secretary and instruct him where to send the VISA ATM CARD to you. Please do let me know immediately you receive the ATM CARD so that we can share the joy. Please my main reason to compensate you with this amount is for you to keep your mouth shut, do not allow anybody to know about this deal ever, let it to be sealed between us because I don't want to have any problem in the future please!. This is how we contributed for your compensation, I contributed $600,000 dollars out of my own share while my new partner contributed, $400,000 dollars to make the total of $1,000,000.00 USD,please let the deal be sealed ok! delete every message you received so far concerning this deal in your mailbox. In the moment, I am very busy here because of the investment projects which me and the new partner are having at hand, finally, remember that I had forwarded instruction to my secretary on your behalf to receive that VISA ATM CARD, so feel free to get in touch with him and he will help you to send it to your address. I will be traveling to Qatar this evening with my partner for an investment project. Regards, Mr. Henri Zongo. Contact my secretary in Burkina-Faso
Contact my secretary in Burkina-Faso
Dear Friend, Good day, this is Mr. Henri Zongo, I'm happy to inform you about my success in getting the fund $29.6Million transferred under the co-operation of a new partner from Dubai, Presently I'm in Dubai for investment projects with my own share of the total sum. Meanwhile,I didn't forget your past efforts and attempts to assist me in transferring those funds despite that it failed us some how. Now contact my secretary in Burkina-Faso, his name is Mr. Leonard Kabore and his email address is (leonard_kab...@outlook.com) and ask him to send you VISA ATM CARD which has loaded the sum of USD$1,000,000.00 (One Million United States Dollars issued in your name by our Bank (BOA) headquarter, this is for your compensation for all the past efforts and attempts to assist me in this matter. Note, you will withdraw your money in an ATM MACHINE in any part of the world, but the maximum is ($5,000) Fifteen Thousand Us Dollars in three transactions per day. So feel free and get in touched with my secretary and instruct him where to send the VISA ATM CARD to you. Please do let me know immediately you receive the ATM CARD so that we can share the joy. Please my main reason to compensate you with this amount is for you to keep your mouth shut, do not allow anybody to know about this deal ever, let it to be sealed between us because I don't want to have any problem in the future please!. This is how we contributed for your compensation, I contributed $600,000 dollars out of my own share while my new partner contributed, $400,000 dollars to make the total of $1,000,000.00 USD,please let the deal be sealed ok! delete every message you received so far concerning this deal in your mailbox. In the moment, I am very busy here because of the investment projects which me and the new partner are having at hand, finally, remember that I had forwarded instruction to my secretary on your behalf to receive that VISA ATM CARD, so feel free to get in touch with him and he will help you to send it to your address. I will be traveling to Qatar this evening with my partner for an investment project. Regards, Mr. Henri Zongo. Contact my secretary in Burkina-Faso
Contact my secretary in Burkina-Faso
Dear Friend, Good day, this is Mr. Henri Zongo, I'm happy to inform you about my success in getting the fund $29.6Million transferred under the co-operation of a new partner from Dubai, Presently I'm in Dubai for investment projects with my own share of the total sum. Meanwhile,I didn't forget your past efforts and attempts to assist me in transferring those funds despite that it failed us some how. Now contact my secretary in Burkina-Faso, his name is Mr. Leonard Kabore and his email address is (leonard_kab...@outlook.com) and ask him to send you VISA ATM CARD which has loaded the sum of USD$1,000,000.00 (One Million United States Dollars issued in your name by our Bank (BOA) headquarter, this is for your compensation for all the past efforts and attempts to assist me in this matter. Note, you will withdraw your money in an ATM MACHINE in any part of the world, but the maximum is ($5,000) Fifteen Thousand Us Dollars in three transactions per day. So feel free and get in touched with my secretary and instruct him where to send the VISA ATM CARD to you. Please do let me know immediately you receive the ATM CARD so that we can share the joy. Please my main reason to compensate you with this amount is for you to keep your mouth shut, do not allow anybody to know about this deal ever, let it to be sealed between us because I don't want to have any problem in the future please!. This is how we contributed for your compensation, I contributed $600,000 dollars out of my own share while my new partner contributed, $400,000 dollars to make the total of $1,000,000.00 USD,please let the deal be sealed ok! delete every message you received so far concerning this deal in your mailbox. In the moment, I am very busy here because of the investment projects which me and the new partner are having at hand, finally, remember that I had forwarded instruction to my secretary on your behalf to receive that VISA ATM CARD, so feel free to get in touch with him and he will help you to send it to your address. I will be traveling to Qatar this evening with my partner for an investment project. Regards, Mr. Henri Zongo. Contact my secretary in Burkina-Faso
Contact my secretary in Burkina-Faso
Dear Friend, Good day, this is Mr. Henri Zongo, I'm happy to inform you about my success in getting the fund $29.6Million transferred under the co-operation of a new partner from Dubai, Presently I'm in Dubai for investment projects with my own share of the total sum. Meanwhile,I didn't forget your past efforts and attempts to assist me in transferring those funds despite that it failed us some how. Now contact my secretary in Burkina-Faso, his name is Mr. Leonard Kabore and his email address is (leonard_kab...@outlook.com) and ask him to send you VISA ATM CARD which has loaded the sum of USD$1,000,000.00 (One Million United States Dollars issued in your name by our Bank (BOA) headquarter, this is for your compensation for all the past efforts and attempts to assist me in this matter. Note, you will withdraw your money in an ATM MACHINE in any part of the world, but the maximum is ($5,000) Fifteen Thousand Us Dollars in three transactions per day. So feel free and get in touched with my secretary and instruct him where to send the VISA ATM CARD to you. Please do let me know immediately you receive the ATM CARD so that we can share the joy. Please my main reason to compensate you with this amount is for you to keep your mouth shut, do not allow anybody to know about this deal ever, let it to be sealed between us because I don't want to have any problem in the future please!. This is how we contributed for your compensation, I contributed $600,000 dollars out of my own share while my new partner contributed, $400,000 dollars to make the total of $1,000,000.00 USD,please let the deal be sealed ok! delete every message you received so far concerning this deal in your mailbox. In the moment, I am very busy here because of the investment projects which me and the new partner are having at hand, finally, remember that I had forwarded instruction to my secretary on your behalf to receive that VISA ATM CARD, so feel free to get in touch with him and he will help you to send it to your address. I will be traveling to Qatar this evening with my partner for an investment project. Regards, Mr. Henri Zongo. Contact my secretary in Burkina-Faso
Contact my secretary in Burkina-Faso
Dear Friend, Good day, this is Mr. Henri Zongo, I'm happy to inform you about my success in getting the fund $29.6Million transferred under the co-operation of a new partner from Dubai, Presently I'm in Dubai for investment projects with my own share of the total sum. Meanwhile,I didn't forget your past efforts and attempts to assist me in transferring those funds despite that it failed us some how. Now contact my secretary in Burkina-Faso, his name is Mr. Leonard Kabore and his email address is (leonard_kab...@outlook.com) and ask him to send you VISA ATM CARD which has loaded the sum of USD$1,000,000.00 (One Million United States Dollars issued in your name by our Bank (BOA) headquarter, this is for your compensation for all the past efforts and attempts to assist me in this matter. Note, you will withdraw your money in an ATM MACHINE in any part of the world, but the maximum is ($5,000) Fifteen Thousand Us Dollars in three transactions per day. So feel free and get in touched with my secretary and instruct him where to send the VISA ATM CARD to you. Please do let me know immediately you receive the ATM CARD so that we can share the joy. Please my main reason to compensate you with this amount is for you to keep your mouth shut, do not allow anybody to know about this deal ever, let it to be sealed between us because I don't want to have any problem in the future please!. This is how we contributed for your compensation, I contributed $600,000 dollars out of my own share while my new partner contributed, $400,000 dollars to make the total of $1,000,000.00 USD,please let the deal be sealed ok! delete every message you received so far concerning this deal in your mailbox. In the moment, I am very busy here because of the investment projects which me and the new partner are having at hand, finally, remember that I had forwarded instruction to my secretary on your behalf to receive that VISA ATM CARD, so feel free to get in touch with him and he will help you to send it to your address. I will be traveling to Qatar this evening with my partner for an investment project. Regards, Mr. Henri Zongo. Contact my secretary in Burkina-Faso
Contact my secretary in Burkina-Faso
Dear Friend, Good day, this is Mr. Henri Zongo, I'm happy to inform you about my success in getting the fund $29.6Million transferred under the co-operation of a new partner from Dubai, Presently I'm in Dubai for investment projects with my own share of the total sum. Meanwhile,I didn't forget your past efforts and attempts to assist me in transferring those funds despite that it failed us some how. Now contact my secretary in Burkina-Faso, his name is Mr. Leonard Kabore and his email address is (leonard_kab...@outlook.com) and ask him to send you VISA ATM CARD which has loaded the sum of USD$1,000,000.00 (One Million United States Dollars issued in your name by our Bank (BOA) headquarter, this is for your compensation for all the past efforts and attempts to assist me in this matter. Note, you will withdraw your money in an ATM MACHINE in any part of the world, but the maximum is ($5,000) Fifteen Thousand Us Dollars in three transactions per day. So feel free and get in touched with my secretary and instruct him where to send the VISA ATM CARD to you. Please do let me know immediately you receive the ATM CARD so that we can share the joy. Please my main reason to compensate you with this amount is for you to keep your mouth shut, do not allow anybody to know about this deal ever, let it to be sealed between us because I don't want to have any problem in the future please!. This is how we contributed for your compensation, I contributed $600,000 dollars out of my own share while my new partner contributed, $400,000 dollars to make the total of $1,000,000.00 USD,please let the deal be sealed ok! delete every message you received so far concerning this deal in your mailbox. In the moment, I am very busy here because of the investment projects which me and the new partner are having at hand, finally, remember that I had forwarded instruction to my secretary on your behalf to receive that VISA ATM CARD, so feel free to get in touch with him and he will help you to send it to your address. I will be traveling to Qatar this evening with my partner for an investment project. Regards, Mr. Henri Zongo. Contact my secretary in Burkina-Faso
Contact Me
RE: RECOVERED FUND. In reference to the signal received from our Investigative Team concerning overdue payments. We write to inform you that some funds have been recovered from some Security Companies, and sub financial houses, meant to be paid out to owners but diverted. However, it was found after due auditing and vetting of all payment files, that your name was tagged on unpaid payment list. Thus, we are informing you that all overdue payments have been approved as shown in our Gazette will be released to you after re-confirmation of your details. 1) Your full name and Address, 2) Phone, fax or mobile. Contact this office directly via Email, Text or Call to speed up payment processing and release. Do discard this information, if you are not the intended recipient. All emails are read and attended. Yours Sincerely, Gabriel
Contact Me
RE: RECOVERED FUND. In reference to the signal received from our Investigative Team concerning overdue payments. We write to inform you that some funds have been recovered from some Security Companies, and sub financial houses, meant to be paid out to owners but diverted. However, it was found after due auditing and vetting of all payment files, that your name was tagged on unpaid payment list. Thus, we are informing you that all overdue payments have been approved as shown in our Gazette will be released to you after re-confirmation of your details. 1) Your full name and Address, 2) Phone, fax or mobile. Contact this office directly via Email, Text or Call to speed up payment processing and release. Do discard this information, if you are not the intended recipient. All emails are read and attended. Yours Sincerely, Gabriel
My name is BOVID EGAVI, a bank's manager in republic of TOGO. I have an abandoned unclaimed sum of thirty-six million euros only. can I trust you with this? if yes then contact me for full details thr
My name is BOVID EGAVI, a bank's manager in republic of TOGO. I have an abandoned unclaimed sum of thirty-six million euros only. can I trust you with this? if yes then contact me for full details thr
CONTACT DHL OFFICE IMMEDIATELY FOR DELIVERY OF YOUR ATM MASTERCARD
Attention; Beneficiary, This is to official inform you that we have been having meetings for the past three (3) weeks which ended two days ago with MR. JIM YONG KIM the Former world bank president and other seven continent presidents on the congress we treated on solution to scam victim problems. Note: we have decided to contact you following the reports we received from anti-fraud international monitoring group your name/email has been submitted to us therefore the united nations have agreed to compensate you with the sum of (USD$1.5 Million) this compensation is also including international business that failed you in past due to government problems etc. We have arranged your payment through our ATM MasterCard and deposited it in DHL Office to deliver it to you which is the latest instruction from the Former World Bank president MR. JIM YONG KIM, For your information’s, the delivery charges already paid by U.N treasury, the only money you will send to DHL office Benin Republic is $225 dollars for security keeping fee, U.N coordinator already paid for others charges fees for delivery except the security keeping fee, the director of DHL refused to collect the security keeping fee from U.N treasury because Direct of DHL office said they don’t know exactly time you will contact them to reconfirm your details to avoid counting demurrage. Therefore be advice to contact DHL Office agent Benin. Rev:Tony harries who is in position to post your ATM MasterCard, contact DHL Office immediately with the bellow email & phone number as listed below. Contact name: Rev:Tony HARRIES Email:(post.dhlbenin.serv...@outlook.com ) Tell: +229-98787436 Make sure you reconfirmed DHL Office your details ASAP as stated below to avoid wrong delivery. Your full name.. Home address:. Your country... Your city.. Telephone.. Occupation:... Age:…….. Let us know as soon as possible you receive your ATM MasterCard for proper verifications. Regards, MR Paul Ogie. DEPUTY SECRETARY-GENERAL (U.N) Benin Republic.
CONTACT DHL OFFICE IMMEDIATELY FOR DELIVERY OF YOUR ATM MASTERCARD
Attention; Beneficiary, This is to official inform you that we have been having meetings for the past three (3) weeks which ended two days ago with MR. JIM YONG KIM the Former world bank president and other seven continent presidents on the congress we treated on solution to scam victim problems. Note: we have decided to contact you following the reports we received from anti-fraud international monitoring group your name/email has been submitted to us therefore the united nations have agreed to compensate you with the sum of (USD$1.5 Million) this compensation is also including international business that failed you in past due to government problems etc. We have arranged your payment through our ATM MasterCard and deposited it in DHL Office to deliver it to you which is the latest instruction from the Former World Bank president MR. JIM YONG KIM, For your information’s, the delivery charges already paid by U.N treasury, the only money you will send to DHL office Benin Republic is $225 dollars for security keeping fee, U.N coordinator already paid for others charges fees for delivery except the security keeping fee, the director of DHL refused to collect the security keeping fee from U.N treasury because Direct of DHL office said they don’t know exactly time you will contact them to reconfirm your details to avoid counting demurrage. Therefore be advice to contact DHL Office agent Benin. Rev:Tony harries who is in position to post your ATM MasterCard, contact DHL Office immediately with the bellow email & phone number as listed below. Contact name: Rev:Tony HARRIES Email:(post.dhlbenin.serv...@outlook.com ) Tell: +229-98787436 Make sure you reconfirmed DHL Office your details ASAP as stated below to avoid wrong delivery. Your full name.. Home address:. Your country... Your city.. Telephone.. Occupation:... Age:…….. Let us know as soon as possible you receive your ATM MasterCard for proper verifications. Regards, MR Paul Ogie. DEPUTY SECRETARY-GENERAL (U.N) Benin Republic.
CONTACT DHL OFFICE IMMEDIATELY FOR DELIVERY OF YOUR ATM MASTERCARD
Attention; Beneficiary, This is to official inform you that we have been having meetings for the past three (3) weeks which ended two days ago with MR. JIM YONG KIM the Former world bank president and other seven continent presidents on the congress we treated on solution to scam victim problems. Note: we have decided to contact you following the reports we received from anti-fraud international monitoring group your name/email has been submitted to us therefore the united nations have agreed to compensate you with the sum of (USD$1.5 Million) this compensation is also including international business that failed you in past due to government problems etc. We have arranged your payment through our ATM MasterCard and deposited it in DHL Office to deliver it to you which is the latest instruction from the Former World Bank president MR. JIM YONG KIM, For your information’s, the delivery charges already paid by U.N treasury, the only money you will send to DHL office Benin Republic is $225 dollars for security keeping fee, U.N coordinator already paid for others charges fees for delivery except the security keeping fee, the director of DHL refused to collect the security keeping fee from U.N treasury because Direct of DHL office said they don’t know exactly time you will contact them to reconfirm your details to avoid counting demurrage. Therefore be advice to contact DHL Office agent Benin. Rev:Tony harries who is in position to post your ATM MasterCard, contact DHL Office immediately with the bellow email & phone number as listed below. Contact name: Rev:Tony HARRIES Email:(post.dhlbenin.serv...@outlook.com ) Tell: +229-98787436 Make sure you reconfirmed DHL Office your details ASAP as stated below to avoid wrong delivery. Your full name.. Home address:. Your country... Your city.. Telephone.. Occupation:... Age:…….. Let us know as soon as possible you receive your ATM MasterCard for proper verifications. Regards, MR Paul Ogie. DEPUTY SECRETARY-GENERAL (U.N) Benin Republic.
