From: Jiri Slaby <jirislaby@kernel.org>
To: Cameron Williams <cang1@live.co.uk>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v3 4/7] tty: 8250: Add support for Intashield IS-100
Date: Mon, 16 Oct 2023 07:40:50 +0200 [thread overview]
Message-ID: <4a1aedbb-0acf-4894-b48b-20eb54d4786f@kernel.org> (raw)
In-Reply-To: <DU0PR02MB7899A8E98A24B0748FA74D59C4D0A@DU0PR02MB7899.eurprd02.prod.outlook.com>
On 15. 10. 23, 19:10, Cameron Williams wrote:
> Add support for the Intashield IS-100 1 port serial card.
>
> Signed-off-by: Cameron Williams <cang1@live.co.uk>
Reviewed-by: Jiri Slaby <jirislaby@kernel.org>
--
js
suse labs
next prev parent reply other threads:[~2023-10-16 5:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BBPatchesV3>
2023-10-15 17:10 ` [PATCH v3 0/7] Brainboxes serial cards additions/fixes Cameron Williams
[not found] ` <20231015171141.3309-1-cang1@live.co.uk>
2023-10-15 17:10 ` [PATCH v3 1/7] tty: 8250: Fix IS-200 PCI ID comment Cameron Williams
2023-10-16 5:37 ` Jiri Slaby
2023-10-16 7:29 ` Cameron Williams
2023-10-15 17:10 ` [PATCH v3 2/7] tty: 8250: Add support for additional Brainboxes UC cards Cameron Williams
2023-10-16 5:40 ` Jiri Slaby
2023-10-16 7:34 ` Cameron Williams
2023-10-15 17:10 ` [PATCH v3 3/7] tty: 8250: Add support for Brainboxes UP cards Cameron Williams
2023-10-16 5:40 ` Jiri Slaby
2023-10-15 17:10 ` [PATCH v3 4/7] tty: 8250: Add support for Intashield IS-100 Cameron Williams
2023-10-16 5:40 ` Jiri Slaby [this message]
2023-10-15 17:10 ` [PATCH v3 5/7] tty: 8250: Add support for and fix up additional Brainboxes PX cards Cameron Williams
2023-10-16 5:41 ` Jiri Slaby
2023-10-15 17:10 ` [PATCH v3 6/7] tty: 8250: Add support for Intashield IX cards Cameron Williams
2023-10-16 5:42 ` Jiri Slaby
2023-10-15 17:10 ` [PATCH v3 7/7] tty: 8250: Add Brainboxes Oxford Semiconductor-based quirks Cameron Williams
2023-10-16 5:44 ` Jiri Slaby
2023-10-16 7:36 ` Cameron Williams
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=4a1aedbb-0acf-4894-b48b-20eb54d4786f@kernel.org \
--to=jirislaby@kernel.org \
--cc=cang1@live.co.uk \
--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.