From: Luis Chamberlain <mcgrof@kernel.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
wireless-regdb@lists.infradead.org
Subject: Re: [PATCH] crda: Makefile: fix .so compilation line with some compilers
Date: Wed, 6 Nov 2019 23:17:49 +0000 [thread overview]
Message-ID: <20191106231749.GM11244@42.do-not-panic.com> (raw)
In-Reply-To: <CA+ASDXMVJg0QSPzSiWFjoDH67yJ-NfYX4MQZUT3gaivx1SJ2aA@mail.gmail.com>
On Wed, Nov 06, 2019 at 08:38:33AM -0800, Brian Norris wrote:
> On Wed, Nov 6, 2019 at 12:12 AM Johannes Berg <johannes@sipsolutions.net> wrote:
> > On Tue, 2019-11-05 at 15:02 -0800, Brian Norris wrote:
> > > Apparently wireless-regdb@ is subscribers only. I have since joined,
> > > but I guess my patch bounced from that list... if I don't hear back in
> > > a while, I may resend.
> >
> > The bigger question is who actually maintains crda now, if anyone ... :)
>
> My mailbox tells me that as of about a year ago, Luis was still
> merging patches. And his latest commit even claims it's "still
> maintained":
>
> As if kernel v4.15 CRDA is no longer needed. Annotate this. The
> code will still be maintained to help older kernels.
Sure, send me patches. Its just not needed on older systems.
Luis
next prev parent reply other threads:[~2019-11-06 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 22:57 [PATCH] crda: Makefile: fix .so compilation line with some compilers Brian Norris
2019-11-05 23:02 ` Brian Norris
2019-11-06 8:12 ` Johannes Berg
2019-11-06 16:38 ` Brian Norris
2019-11-06 23:17 ` Luis Chamberlain [this message]
2019-11-07 17:37 ` [RESEND PATCH] " Brian Norris
2019-11-12 22:45 ` Luis Chamberlain
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=20191106231749.GM11244@42.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=briannorris@chromium.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=wireless-regdb@lists.infradead.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).