From: Arnd Bergmann <arnd@arndb.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Peter Hurley <peter@hurleysoftware.com>
Subject: [PATCH v3 0/5] serial: 8250: fixes for modular build
Date: Wed, 17 Feb 2016 16:02:30 +0100 [thread overview]
Message-ID: <1455721357-4008289-1-git-send-email-arnd@arndb.de> (raw)
Hi Greg,
This is a resend of my last week's 8250 series, with a couple of
issues fixed as pointed out by Paul Gortmaker.
Masahiro Yamada had an idea for a nicer solution to the problem of
a modular build, but after some back and forth, the conclusion was
that this does not work any more after the rework done by
Peter Hurley, so we are back to my original approach.
I've done many compile tests over the last week and found another
corner case in the Ingenic driver patch, which is now also fixed,
and I'm no longer getting any invalid symbol references here or
in other drivers.
Arnd
next reply other threads:[~2016-02-17 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 15:02 Arnd Bergmann [this message]
2016-02-17 15:02 ` [PATCH v3 1/5] Revert "drivers/tty/serial: make 8250/8250_mtk.c explicitly non-modular" Arnd Bergmann
2016-02-17 17:19 ` Matthias Brugger
2016-02-17 15:02 ` [PATCH v3 2/5] Revert "drivers/tty/serial: make 8250/8250_ingenic.c " Arnd Bergmann
2016-02-17 15:02 ` [PATCH v3 3/5] serial: 8250/uniphier: fix modular build Arnd Bergmann
2016-02-17 15:02 ` [PATCH v3 4/5] serial: 8250/ingenic: fix building with SERIAL_8250=m Arnd Bergmann
2016-02-17 15:02 ` [PATCH v3 5/5] serial: 8250/mediatek: " Arnd Bergmann
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=1455721357-4008289-1-git-send-email-arnd@arndb.de \
--to=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=peter@hurleysoftware.com \
--cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®