From: andy.shevchenko@gmail.com
To: "5dd9f8b0c1dc154c73fb883cb948768ae68d1ccb.camel@sealevel.com"
<5dd9f8b0c1dc154c73fb883cb948768ae68d1ccb.camel@sealevel.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Darren Beeson <darren.beeson@sealevel.com>,
Jeff Baldwin <jeff.baldwin@sealevel.com>,
Ryan Wenglarz <ryan.wenglarz@sealevel.com>
Subject: Re: [PATCH V2] serial: exar: Preserve FCTR[5] bit in pci_xr17v35x_setup()
Date: Thu, 22 Feb 2024 00:58:43 +0200 [thread overview]
Message-ID: <ZdaAI4uZ1Byx2cWs@surfacebook.localdomain> (raw)
In-Reply-To: <a9519d301f542c921260b11b4576cd68cc929b52.camel@sealevel.com>
Wed, Feb 21, 2024 at 09:16:46PM +0000, Matthew Howell kirjoitti:
> Allows the use of the EN485 hardware pin by preserving the value of
> FCTR[5] in pci_xr17v35x_setup().
>
> Per the XR17V35X datasheet, the EN485 hardware pin works by setting
> FCTR[5] when the pin is active. pci_xr17v35x_setup() prevented the use
> of EN485 because it overwrote the FCTR register.
First of all, please avoid In-Reply-to: for the new versions of the change,
i.o.w. new version — new email thread.
Second, the above commit message sounds like a fix. Does it deserve Fixes tag?
...
> unsigned int baud = 7812500;
> u8 __iomem *p;
> int ret;
> + u8 en485mask;
Please, preserve reversed xmas tree order.
unsigned int baud = 7812500;
u8 __iomem *p;
u8 en485mask;
int ret;
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-02-21 22:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 21:06 [PATCH V1] serial: exar: Preserve FCTR[5] bit in pci_xr17v35x_setup() Matthew Howell
2024-02-21 21:16 ` [PATCH V2] " Matthew Howell
2024-02-21 22:58 ` andy.shevchenko [this message]
2024-04-09 13:01 ` Matthew Howell
2024-04-08 13:11 ` Matthew Howell
2024-04-08 14:56 ` gregkh
2024-04-09 12:33 ` Matthew Howell
2024-04-08 16:48 ` Ilpo Järvinen
2024-04-08 17:25 ` Ilpo Järvinen
2024-04-08 20:27 ` Matthew Howell
2024-04-10 13:49 ` Ilpo Järvinen
2024-04-10 16:20 ` Matthew Howell
2024-04-11 8:27 ` Ilpo Järvinen
2024-04-11 17:01 ` Matthew Howell
2024-04-11 20:44 ` Matthew Howell
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=ZdaAI4uZ1Byx2cWs@surfacebook.localdomain \
--to=andy.shevchenko@gmail.com \
--cc=5dd9f8b0c1dc154c73fb883cb948768ae68d1ccb.camel@sealevel.com \
--cc=darren.beeson@sealevel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeff.baldwin@sealevel.com \
--cc=linux-serial@vger.kernel.org \
--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 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.