From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Li Chen <lchen@ambarella.com>
Cc: "Kishon Vijay Abraham I" <kishon@ti.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXT] Re: [PATCH] misc: pci_endpoint_test: simplify endpoint test read and write operations
Date: Thu, 20 Jan 2022 09:42:02 +0100 [thread overview]
Message-ID: <YekgWmTSzCi2gTMs@kroah.com> (raw)
In-Reply-To: <SA1PR19MB5572D993FFC2EECDA89E5A66A05A9@SA1PR19MB5572.namprd19.prod.outlook.com>
On Thu, Jan 20, 2022 at 08:25:51AM +0000, Li Chen wrote:
> > -----Original Message-----
> > From: Greg Kroah-Hartman [mailto:gregkh@linuxfoundation.org]
> > Sent: Thursday, January 20, 2022 4:17 PM
> > To: Li Chen
> > Cc: Kishon Vijay Abraham I; Lorenzo Pieralisi; Krzysztof Wilczyński; Arnd
> > Bergmann; Bjorn Helgaas; linux-pci@vger.kernel.org; linux-
> > kernel@vger.kernel.org
> > Subject: Re: [EXT] Re: [PATCH] misc: pci_endpoint_test: simplify endpoint test
> > read and write operations
> >
> > On Thu, Jan 20, 2022 at 08:09:20AM +0000, Li Chen wrote:
> > > > -----Original Message-----
> > > > From: Greg Kroah-Hartman [mailto:gregkh@linuxfoundation.org]
> > > > Sent: Thursday, January 20, 2022 4:06 PM
> > > > To: Li Chen
> > > > Cc: Kishon Vijay Abraham I; Lorenzo Pieralisi; Krzysztof Wilczyński; Arnd
> > > > Bergmann; Bjorn Helgaas; linux-pci@vger.kernel.org; linux-
> > > > kernel@vger.kernel.org
> > > > Subject: [EXT] Re: [PATCH] misc: pci_endpoint_test: simplify endpoint test
> > read
> > > > and write operations
> > > >
> > > > On Thu, Jan 20, 2022 at 08:03:17AM +0000, Li Chen wrote:
> > > > >
> > > >
> > **************************************************************
> > > > ********
> > > > > This email and attachments contain Ambarella Proprietary and/or
> > Confidential
> > > > Information and is intended solely for the use of the individual(s) to whom it
> > is
> > > > addressed. Any unauthorized review, use, disclosure, distribute, copy, or
> > print is
> > > > prohibited. If you are not an intended recipient, please contact the sender by
> > > > reply email and destroy all copies of the original message. Thank you.
> > > >
> > > > Now deleted.
> > >
> > > Hi, Greg
> > >
> > > I'm sorry that I have no way to remove this message by myself.
> >
> > Sorry, but patches/emails with that notice on it are not allowed to be
> > accepted for obvious reasons. Please work with your company to fix
> > this.
>
> Ok, thanks! So, should I resend this patch after fixing this self-attached message with my company?
As the original is not acceptable, yes, please do.
next prev parent reply other threads:[~2022-01-20 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 8:03 Li Chen
2022-01-20 8:06 ` Greg Kroah-Hartman
2022-01-20 8:09 ` [EXT] " Li Chen
2022-01-20 8:17 ` Greg Kroah-Hartman
2022-01-20 8:25 ` Li Chen
2022-01-20 8:42 ` Greg Kroah-Hartman [this message]
2022-01-20 10:06 ` Li Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YekgWmTSzCi2gTMs@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=lchen@ambarella.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome