From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752416AbdATW34 (ORCPT <rfc822;w@1wt.eu>);
        Fri, 20 Jan 2017 17:29:56 -0500
Received: from mail-qk0-f193.google.com ([209.85.220.193]:36376 "EHLO
        mail-qk0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751201AbdATW3x (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 20 Jan 2017 17:29:53 -0500
MIME-Version: 1.0
In-Reply-To: <1484864602-5266-3-git-send-email-sudipm.mukherjee@gmail.com>
References: <1484864602-5266-1-git-send-email-sudipm.mukherjee@gmail.com> <1484864602-5266-3-git-send-email-sudipm.mukherjee@gmail.com>
From: Andy Shevchenko <andy.shevchenko@gmail.com>
Date: Sat, 21 Jan 2017 00:29:31 +0200
Message-ID: <CAHp75VdgtLUY4PRq=k2Yn2zf+WyYt1bVxtJ+zUtywhe4uwj5fw@mail.gmail.com>
Subject: Re: [PATCH v10 3/3] serial: 8250_pci: remove exar code
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
        Alexandre Courbot <gnurou@gmail.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Jiri Slaby <jslaby@suse.com>,
        One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
        "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Jan 20, 2017 at 12:23 AM, Sudip Mukherjee
<sudipm.mukherjee@gmail.com> wrote:
> From: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
>
> Remove the Exar specific codes from 8250_pci and blacklist those chips
> so that the new Exar serial driver binds to the devices.

> patch4? but those are from different vendor. They are with
> PCI_VENDOR_ID_COMMTECH. Then we should not name the file as 8250_exar.

But it seems it is using Exar behind the scenes. No?

> But if needed I can send a separate patch for that after this series is
> complete.

For me looks like logical continuation to this series. I'm fine with
separate patch later on.

-- 
With Best Regards,
Andy Shevchenko