From: "Michael Büsch" <m@bues.ch>
To: "Rafał Miłecki" <rafal@milecki.pl>
Cc: "Kalle Valo" <kvalo@codeaurora.org>,
"Larry Finger" <Larry.Finger@lwfinger.net>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Matt Redfearn" <matt.redfearn@mips.com>,
linux-wireless@vger.kernel.org,
"Hauke Mehrtens" <hauke@hauke-m.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 1/2] Revert "ssb: Prevent build of PCI host features in module"
Date: Sat, 12 May 2018 12:14:58 +0200 [thread overview]
Message-ID: <20180512121458.58570198@wiggum> (raw)
In-Reply-To: <2a401060858a337f84039eddef4b3b87@milecki.pl>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
On Sat, 12 May 2018 12:00:07 +0200
Rafał Miłecki <rafal@milecki.pl> wrote:
> > Yes, I'm OK with the patch, if we have a third patch that cleans up the
> > PCI_DRIVERS_LEGACY dependency by moving it to SSB_PCICORE_HOSTMODE
> > where it belongs. (This doesn't need to go into the stable tree.)
> > We currently implicitly get that via dependency chain, so this is OK
> > for now as-is.
>
> I'm planning to handle PCI_DRIVERS_LEGACY cleanup once my patches hit
> net-next.git and then wireless-drivers-next.git. It's to avoid
> conflicts.
Yes, thanks. Take your time. We're not in a hurry. :)
This change should not make a functional difference.
--
Michael
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-05-12 10:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 9:17 [PATCH V2 1/2] Revert "ssb: Prevent build of PCI host features in module" Rafał Miłecki
2018-05-11 9:17 ` [PATCH V2 2/2] ssb: make SSB_PCICORE_HOSTMODE depend on SSB = y Rafał Miłecki
2018-05-11 9:21 ` [PATCH V2 1/2] Revert "ssb: Prevent build of PCI host features in module" Rafał Miłecki
2018-05-11 9:21 ` Rafał Miłecki
2018-05-11 10:13 ` Kalle Valo
2018-05-11 10:13 ` Kalle Valo
2018-05-11 10:25 ` Rafał Miłecki
2018-05-11 10:25 ` Rafał Miłecki
2018-05-11 12:08 ` Larry Finger
2018-05-12 7:50 ` Kalle Valo
2018-05-12 7:50 ` Kalle Valo
2018-05-12 8:01 ` Michael Büsch
2018-05-12 10:00 ` Rafał Miłecki
2018-05-12 10:14 ` Michael Büsch [this message]
2018-05-12 8:40 ` [V2, " Kalle Valo
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=20180512121458.58570198@wiggum \
--to=m@bues.ch \
--cc=Larry.Finger@lwfinger.net \
--cc=hauke@hauke-m.de \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matt.redfearn@mips.com \
--cc=rafal@milecki.pl \
--cc=zajec5@gmail.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.