All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: Jochen Mades <jochen@mades.net>, Lukas Wunner <lukas@wunner.de>
Cc: gregkh@linuxfoundation.org, Russell King <linux@armlinux.org.uk>,
	Jiri Slaby <jirislaby@kernel.org>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	Philipp Rosenberger <p.rosenberger@kunbus.com>
Subject: Re: [PATCH] Bugfix RTS line config in RS485 mode is overwritten in pl011_set_mctrl() function.
Date: Wed, 12 Jan 2022 02:41:31 +0100	[thread overview]
Message-ID: <21c124f6-43a2-7ac8-2fde-a7bebacec459@gmx.de> (raw)
In-Reply-To: <27017560.2684465.1641895232612@webmail.strato.com>

Hi Jochen,

On 11.01.22 at 11:00, Jochen Mades wrote:
> Hi Lukas, Lino,
>
> please let me know when I could test again with an "official" linux kernel, instead of using my local patch.
>
> Bests
> Jochen

While the fix itself looks good so far there are still some style issue as Lukas pointed out. These issues
have to be fixed before the patch can be accepted for mainline integration. Please have a look at
Documentation/process/submitting-patches.rst for the correct patch format. After these issues are fixed
please send the patch as a v2, so we can review the new version.

Best regards,
Lino


  reply	other threads:[~2022-01-12  1:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31 17:15 [PATCH] Bugfix RTS line config in RS485 mode is overwritten in pl011_set_mctrl() function jmades
2022-01-02 10:07 ` Lukas Wunner
2022-01-02 15:06   ` Lino Sanfilippo
2022-01-02 18:28     ` Lukas Wunner
2022-01-03 13:44       ` Lino Sanfilippo
2022-01-11 10:00       ` Jochen Mades
2022-01-12  1:41         ` Lino Sanfilippo [this message]
2022-01-13 10:12   ` Jochen Mades
2022-01-13 10:20     ` Greg KH
2022-01-23  4:32     ` 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=21c124f6-43a2-7ac8-2fde-a7bebacec459@gmx.de \
    --to=linosanfilippo@gmx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=jochen@mades.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lukas@wunner.de \
    --cc=p.rosenberger@kunbus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.