From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ivan Sistik <sistik@3ksolutions.sk>
Cc: Jiri Slaby <jslaby@suse.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Scott Branden <sbranden@broadcom.com>,
Stefan Wahren <wahrenst@gmx.net>,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] tty: serial: amba-pl011: added RS485 support
Date: Mon, 28 Dec 2020 16:13:44 +0100 [thread overview]
Message-ID: <X+n2KCMCR9l1bZyk@kroah.com> (raw)
In-Reply-To: <20201221231848.55259-1-sistik@3ksolutions.sk>
On Tue, Dec 22, 2020 at 12:18:48AM +0100, Ivan Sistik wrote:
> This patch is ported and corrected version of my previous patch which can
> be reviewed here:
> https://lore.kernel.org/lkml/20200106235203.27256-1-sistik@3ksolutions.sk/
>
> I have been waiting for some time to see if Lukas Wunner <lukas@wunner.de>
> will create patch with his own solution.
>
> Now I am successfully running my imeplementation for almost one year in
> production environment. There are no problems with it. I have made
> corrections to patch according to notes from Greg Kroah-Hartman
> <gregkh@linuxfoundation.org>.
>
> Patch content:
All of the above should not be in the changelog body, but rather below
the --- line.
Please fix this up and resend a v2 with that moved so I don't have to
hand-edit the patch to be able to apply it!
thanks,
greg k-h
next prev parent reply other threads:[~2020-12-28 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 23:18 [PATCH] tty: serial: amba-pl011: added RS485 support Ivan Sistik
2020-12-28 15:13 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-06 23:52 Ivan Sistik
2020-01-07 7:27 ` Greg Kroah-Hartman
2020-01-17 0:31 ` Ivan Sistik - 3K Solutions, s. r. o.
2020-01-07 7:28 ` Greg Kroah-Hartman
2020-01-16 13:29 ` Lukas Wunner
2020-01-17 0:58 ` Ivan Šištík - 3K Solutions, s. r. o.
2020-01-21 8:49 ` Lukas Wunner
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=X+n2KCMCR9l1bZyk@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=sbranden@broadcom.com \
--cc=sistik@3ksolutions.sk \
--cc=suravee.suthikulpanit@amd.com \
--cc=wahrenst@gmx.net \
/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;
as well as URLs for NNTP newsgroup(s).