From: David Miller <davem@davemloft.net>
To: arnd@arndb.de
Cc: netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-pcmcia@lists.infradead.org, kas@fi.muni.cz,
jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH 0/4] net: driver fixes from arm randconfig builds
Date: Thu, 29 Jan 2015 15:08:59 -0800 (PST) [thread overview]
Message-ID: <20150129.150859.1312045066060618087.davem@davemloft.net> (raw)
In-Reply-To: <1422454504-439085-1-git-send-email-arnd@arndb.de>
From: Arnd Bergmann <arnd@arndb.de>
Date: Wed, 28 Jan 2015 15:15:00 +0100
> These four patches are fallout from test builds on ARM. I have a
> few more of them in my backlog but have not yet confirmed them
> to still be valid.
>
> The first three patches are about incomplete dependencies on
> old drivers. One could backport them to the beginning of time
> in theory, but there is little value since nobody would run into
> these problems.
>
> The final patch is one I had submitted before together with the
> respective pcmcia patch but forgot to follow up on that. It's
> still a valid but relatively theoretical bug, because the previous
> behavior of the driver was just as broken as what we have in
> mainline.
Series applied, thanks Arnd.
prev parent reply other threads:[~2015-01-29 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 14:15 [PATCH 0/4] net: driver fixes from arm randconfig builds Arnd Bergmann
2015-01-28 14:15 ` [PATCH 1/4] net: cs89x0: always build platform code if !HAS_IOPORT_MAP Arnd Bergmann
2015-01-28 14:15 ` [PATCH 2/4] net: wan: add missing virt_to_bus dependencies Arnd Bergmann
2015-01-28 16:19 ` Jan Kasprzak
2015-01-28 14:15 ` [PATCH 3/4] net: lance,ni64: don't build for ARM Arnd Bergmann
2015-01-28 14:15 ` [PATCH 4/4] net: am2150: fix nmclan_cs.c shared interrupt handling Arnd Bergmann
2015-01-29 23:08 ` David Miller [this message]
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=20150129.150859.1312045066060618087.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kas@fi.muni.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=netdev@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).