From: Greg KH <gregkh@linuxfoundation.org>
To: Matthew Howell <matthew.howell@sealevel.com>
Cc: linux-serial@vger.kernel.org, jeff.baldwin@sealevel.com,
ryan.wenglarz@sealevel.com
Subject: Re: [PATCH] serial: exar: Fix GPIO configuration for Sealevel cards based on XR17V35X
Date: Fri, 10 Jul 2020 15:19:41 +0200 [thread overview]
Message-ID: <20200710131941.GA1824558@kroah.com> (raw)
In-Reply-To: <568e88c6-6f66-c9d0-b692-f15698a13577@sealevel.com>
On Fri, Jul 10, 2020 at 09:13:19AM -0400, Matthew Howell wrote:
>
> Could you clarify what info was not acceptable? And was the whole patch deleted/rejected, or just the
> info removed?
Your email footer is not compatible with public kernel development.
prev parent reply other threads:[~2020-07-10 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 19:23 [PATCH] serial: exar: Fix GPIO configuration for Sealevel cards based on XR17V35X Matthew Howell
2020-07-10 12:40 ` Greg KH
2020-07-10 12:41 ` Greg KH
2020-07-10 13:13 ` Matthew Howell
2020-07-10 13:19 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200710131941.GA1824558@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jeff.baldwin@sealevel.com \
--cc=linux-serial@vger.kernel.org \
--cc=matthew.howell@sealevel.com \
--cc=ryan.wenglarz@sealevel.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