From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Michal Simek <michal.simek@xilinx.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Sam Povilus <kernel.development@povil.us>,
linux-arm-kernel@lists.infradead.org,
linux-serial@vger.kernel.org, jslaby@suse.com,
soren.brinkmann@xilinx.com
Subject: Re: [PATCH 1/1] xilinx ps uart: Adding a kernel parameter for the number of xilinx ps uarts
Date: Thu, 25 May 2017 14:29:20 +0100 [thread overview]
Message-ID: <20170525142920.1d662467@alans-desktop> (raw)
In-Reply-To: <b5a032c8-db86-c16b-750f-10aa2a132248@xilinx.com>
> Ok. Is there any problem if uart_register_driver is called for every
> instance separately with nr=1? This driver has major 0, minor 0. Based
If you are doing that level of code restructuring none that I am aware
of, and if you find one I'm happy to work on fixing it.
Alan
WARNING: multiple messages have this Message-ID (diff)
From: gnomes@lxorguk.ukuu.org.uk (Alan Cox)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] xilinx ps uart: Adding a kernel parameter for the number of xilinx ps uarts
Date: Thu, 25 May 2017 14:29:20 +0100 [thread overview]
Message-ID: <20170525142920.1d662467@alans-desktop> (raw)
In-Reply-To: <b5a032c8-db86-c16b-750f-10aa2a132248@xilinx.com>
> Ok. Is there any problem if uart_register_driver is called for every
> instance separately with nr=1? This driver has major 0, minor 0. Based
If you are doing that level of code restructuring none that I am aware
of, and if you find one I'm happy to work on fixing it.
Alan
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Michal Simek <michal.simek@xilinx.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Sam Povilus <kernel.development@povil.us>,
<gregkh@linuxfoundation.org>, <jslaby@suse.com>,
<soren.brinkmann@xilinx.com>, <linux-serial@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] xilinx ps uart: Adding a kernel parameter for the number of xilinx ps uarts
Date: Thu, 25 May 2017 14:29:20 +0100 [thread overview]
Message-ID: <20170525142920.1d662467@alans-desktop> (raw)
In-Reply-To: <b5a032c8-db86-c16b-750f-10aa2a132248@xilinx.com>
> Ok. Is there any problem if uart_register_driver is called for every
> instance separately with nr=1? This driver has major 0, minor 0. Based
If you are doing that level of code restructuring none that I am aware
of, and if you find one I'm happy to work on fixing it.
Alan
next prev parent reply other threads:[~2017-05-25 13:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 2:21 [PATCH 1/1] xilinx ps uart: Adding a kernel parameter for the number of xilinx ps uarts Sam Povilus
2017-05-20 2:21 ` Sam Povilus
2017-05-20 16:20 ` Alan Cox
2017-05-20 16:20 ` Alan Cox
2017-05-20 16:20 ` Alan Cox
2017-05-22 7:02 ` Michal Simek
2017-05-22 7:02 ` Michal Simek
2017-05-22 7:02 ` Michal Simek
2017-05-22 18:26 ` Alan Cox
2017-05-22 18:26 ` Alan Cox
2017-05-22 18:26 ` Alan Cox
2017-05-23 11:44 ` Michal Simek
2017-05-23 11:44 ` Michal Simek
2017-05-23 11:44 ` Michal Simek
2017-05-23 20:07 ` Alan Cox
2017-05-23 20:07 ` Alan Cox
2017-05-23 20:07 ` Alan Cox
2017-05-24 13:06 ` Michal Simek
2017-05-24 13:06 ` Michal Simek
2017-05-24 13:06 ` Michal Simek
2017-05-24 13:31 ` Alan Cox
2017-05-24 13:31 ` Alan Cox
2017-05-24 13:31 ` Alan Cox
2017-05-24 16:09 ` Michal Simek
2017-05-24 16:09 ` Michal Simek
2017-05-24 16:09 ` Michal Simek
2017-05-25 9:27 ` Maarten Brock
2017-05-25 9:27 ` Maarten Brock
2017-05-25 9:27 ` Maarten Brock
2017-05-25 13:29 ` Alan Cox [this message]
2017-05-25 13:29 ` Alan Cox
2017-05-25 13:29 ` Alan Cox
2017-05-25 15:33 ` Michal Simek
2017-05-25 15:33 ` Michal Simek
2017-05-25 15:33 ` Michal Simek
2017-05-24 3:27 ` Sam Povilus
2017-05-24 3:27 ` Sam Povilus
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=20170525142920.1d662467@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kernel.development@povil.us \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=soren.brinkmann@xilinx.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.