linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Helge Deller <deller@gmx.de>,
	Frank Scheiner <frank.scheiner@web.de>,
	linux-parisc@vger.kernel.org,
	John David Anglin <dave.anglin@bell.net>,
	linux-serial@vger.kernel.org
Cc: debian-hppa@lists.debian.org
Subject: Re: Have my PA8800 back online... (serial port missing on v4.14)
Date: Tue, 19 Dec 2017 12:53:04 +0200	[thread overview]
Message-ID: <1513680784.7000.170.camel@linux.intel.com> (raw)
In-Reply-To: <ebe416dd-aa18-9433-4dd7-67490d5778ee@gmx.de>

On Mon, 2017-12-18 at 21:07 +0100, Helge Deller wrote:
> Hi Andy,
> 
> On 13.12.2017 16:16, Andy Shevchenko wrote:
> > On Tue, 2017-12-12 at 21:11 +0100, Helge Deller wrote:
> > > On 11.12.2017 09:26, Andy Shevchenko wrote:
> > > > 
> > > Thanks for the offer to accept this patch, but maybe we are able
> > > to come up with another patch which simply hides those unsupported
> > > devices (serial port and ATI graphics card device on the Diva
> > > card).
> > > I posted a proposed patch here:
> > > http://www.spinics.net/lists/linux-parisc/msg08187.html
> > 
> > Reading briefly that one I guess it's even better (now I realized
> > you
> > even do not have connectors of those devices outside).
> 
> It's now fixed for parisc by new PCI quirks which
> disable the parisc serial AUX port: 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/com
> mit/?id=bcf3f1752a622f1372d3252d0fea8855d89812e7

Thank you for taking care of this.

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2017-12-19 10:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2ADB5C8A-DFEB-4CA5-92BA-96E459A3575E@bell.net>
     [not found] ` <8314a5d6-7df7-3282-0d91-a9b414a122e0@web.de>
     [not found]   ` <526274E4-88D8-4DF8-8F74-5B775186BBEC@bell.net>
     [not found]     ` <cc22ee64-e9f3-aeb4-a9a0-a503f20f9634@web.de>
     [not found]       ` <48320506-f7fa-822b-fb45-40eab1dbda02@bell.net>
     [not found]         ` <17707adb-4f71-1d66-2a19-3cdfaff047f3@gmx.de>
     [not found]           ` <53815372-58e8-70e2-bab4-1777e848cf5e@web.de>
2017-12-08 19:06             ` Have my PA8800 back online... (serial port missing on v4.14) Helge Deller
2017-12-11  8:26               ` Andy Shevchenko
2017-12-12 20:11                 ` Helge Deller
2017-12-13 15:16                   ` Andy Shevchenko
2017-12-18 20:07                     ` Helge Deller
2017-12-19 10:53                       ` Andy Shevchenko [this message]
     [not found]             ` <79c110ec-2975-a827-4b9d-1351ab77779b@gmx.de>
     [not found]               ` <d3c1e035-6486-c0b5-e87a-22d26c0c95f5@bell.net>
2017-12-09 21:03                 ` Have my PA8800 back online Helge Deller
     [not found]                   ` <897B27DE-04A1-4906-8DF2-C037393139C3@bell.net>
2017-12-11 14:46                     ` Helge Deller
2017-12-11 15:25                       ` John David Anglin
2017-12-12 15:59                       ` John David Anglin
2017-12-12 20:52                         ` Helge Deller

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=1513680784.7000.170.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=dave.anglin@bell.net \
    --cc=debian-hppa@lists.debian.org \
    --cc=deller@gmx.de \
    --cc=frank.scheiner@web.de \
    --cc=linux-parisc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).