[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <PH0PR11MB509619A1023CD03AB03C15A09B369@PH0PR11MB5096.namprd11.prod.outlook.com>
Date: Tue, 1 Nov 2022 18:10:00 +0000
From: <Tharunkumar.Pasumarthi@...rochip.com>
To: <ilpo.jarvinen@...ux.intel.com>, <andy.shevchenko@...il.com>
CC: <Kumaravel.Thiagarajan@...rochip.com>,
<gregkh@...uxfoundation.org>, <jirislaby@...nel.org>,
<u.kleine-koenig@...gutronix.de>, <johan@...nel.org>,
<wander@...hat.com>, <etremblay@...tech-controls.com>,
<macro@...am.me.uk>, <geert+renesas@...der.be>, <jk@...abs.org>,
<phil.edworthy@...esas.com>, <lukas@...ner.de>,
<linux-kernel@...r.kernel.org>, <linux-serial@...r.kernel.org>,
<UNGLinuxDriver@...rochip.com>
Subject: RE: [PATCH v2 tty-next 2/3] 8250: microchip: pci1xxxx: Add rs485
support to quad-uart driver.
> From: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
> Sent: Tuesday, November 1, 2022 9:20 PM
> To: Andy Shevchenko <andy.shevchenko@...il.com>
> Subject: Re: [PATCH v2 tty-next 2/3] 8250: microchip: pci1xxxx: Add rs485
> support to quad-uart driver.
>
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> There have been perhaps one of those things I pointed out that was added
> later than the others but it won't explain why nothing was found from the
> code.
Sorry Ilpo. This was a mistake from my side. I was referring to older kernel instead of the one in tty-next branch by mistake. I will make sure not to repeat this going forward.
Thanks,
Tharun Kumar P
Powered by blists - more mailing lists