From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Roberto Manuel SARA <rmsara@matis.onmicrosoft.com>
Cc: "jslaby@suse.com" <jslaby@suse.com>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: drivers/tty/serial/max310x doesn't support latest UART revision of MAX14830
Date: Wed, 19 Oct 2016 10:18:59 +0200 [thread overview]
Message-ID: <20161019081859.GA5747@kroah.com> (raw)
In-Reply-To: <VI1PR0501MB2093567C1DB630B743CD0A0092D20@VI1PR0501MB2093.eurprd05.prod.outlook.com>
On Wed, Oct 19, 2016 at 08:12:13AM +0000, Roberto Manuel SARA wrote:
> Confidentiality Warning: This message and any
> attachments are intended only for the use of the intended recipient(s), are
> confidential, and may be privileged. If you are not the intended recipient, you
> are hereby notified that any review, retransmission, conversion to hard copy,
> copying, circulation or other use of this message and any attachments is
> strictly prohibited. If you are not the intended recipient, please notify the
> sender immediately by return e-mail, and delete this message and any
> attachments from your system. Thank-you.
I am not allowed to respond to such emails as it is not compatible with
doing work in the open for Linux. Please remove and I will be glad to
reply.
thanks,
greg k-h
next parent reply other threads:[~2016-10-19 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <VI1PR0501MB2093567C1DB630B743CD0A0092D20@VI1PR0501MB2093.eurprd05.prod.outlook.com>
2016-10-19 8:18 ` gregkh [this message]
2016-10-19 15:03 ` drivers/tty/serial/max310x doesn't support latest UART revision of MAX14830 Uwe Kleine-König
2016-10-19 16:03 ` gregkh
[not found] <CAHv5Snq5T6KtQ_kbmjHOtfS1-F_N2rm_SHTWqfdpywHQaVvG5Q@mail.gmail.com>
2016-10-19 8:32 ` Greg KH
[not found] ` <CAHv5SnojBcEbuLJzLNS76PY0=EB+=Cvb-ZUmTfyeikJ224t23Q@mail.gmail.com>
2016-10-19 9:14 ` Greg KH
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=20161019081859.GA5747@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rmsara@matis.onmicrosoft.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