All of lore.kernel.org
 help / color / mirror / Atom feed
From: Je Yen Tam <je.yen.tam@ni.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Re: [PATCH] Revert "serial/8250: Add support for NI-Serial PXI/PXIe+485 devices"
Date: Wed, 27 Nov 2019 07:23:39 +0000	[thread overview]
Message-ID: <MN2PR04MB5920DA1BBA0AF9D07E48EAC1B7440@MN2PR04MB5920.namprd04.prod.outlook.com> (raw)
In-Reply-To: <20191127065903.GA1725222@kroah.com>

> Subject: [EXTERNAL] Re: [PATCH] Revert "serial/8250: Add support for NI-Serial
> PXI/PXIe+485 devices"
> 
> On Wed, Nov 27, 2019 at 11:17:51AM +0800, Je Yen Tam wrote:
> > This reverts commit fdc2de87124f5183a98ea7eced1f76dbdba22951 which is
> > commit 225607f75454 ("serial/8250: Add support for NI-Serial PXI/PXIe+485
> devices").
> 
> That sentance does not make sense.  fdc2de87124f ("serial/8250: Add support for
> NI-Serial PXI/PXIe+485 devices") is in the 5.4 kernel tree, where did the commit id
> "225607f75454" come from?  I don't see it anywhere in Linus's tree.

Overlooked the commit 225607f75454 which only visible to my own branch, will 
remove it, sorry for the confusion.

> > The upstream introduced a breakage on NI-Serial PXI(e)-RS485 devices,
> > RS-232 variants have no issue. The Linux system can enumerate the
> > Serial
> > PXI(e)-RS485 devices, but it broke the R/W operation on the ports.
> 
> I can not parse this paragraph either, what do you mean by "The upstream"?

"The upstream" actually means the commit fdc2de87124f. To be more specific, will
rephrase it to "The commit fdc2de87124f".

> > However, the implementation is working on the NI internal Linux RT
> > kernel but it does not work in the Linux main tree kernel. This is
> > only affecting NI products, specifically the RS-485 variants.
> > Reverting the upstream until a proper implementation that can apply to
> > both NI internal Linux kernel and Linux mainline kernel is figured out.
> 
> So this patch really does not work at all?  Can't you just find a simple fix to go on top
> of it to resolve the issue?  You really want it all ripped out for 5.5 and 5.4.y?

It does work in NI Linux kernel but not in generic Linux kernel from the main tree, NI's
Serial team's decision is to have a cleaner implementation so decided to rip out all of it
for 5.5 and 5.4.y to prevent unexpected breakage.

> thanks,
> 
> greg k-h

  reply	other threads:[~2019-11-27  7:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27  3:17 [PATCH] Revert "serial/8250: Add support for NI-Serial PXI/PXIe+485 devices" Je Yen Tam
2019-11-27  6:59 ` Greg KH
2019-11-27  7:23   ` Je Yen Tam [this message]
2019-11-27  7:43     ` 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=MN2PR04MB5920DA1BBA0AF9D07E48EAC1B7440@MN2PR04MB5920.namprd04.prod.outlook.com \
    --to=je.yen.tam@ni.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    /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.