From: Kalle Valo <kvalo@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org, linux-mips@linux-mips.org,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-kernel@vger.kernel.org, "Michael Buesch" <m@bues.ch>,
netdev@vger.kernel.org
Subject: Re: [PATCH, RESEND] ssb: mark ssb_bus_register as __maybe_unused
Date: Sat, 16 Jan 2016 14:10:31 +0200 [thread overview]
Message-ID: <87bn8l7miw.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <4037550.DMaVTE01Aq@wuerfel> (Arnd Bergmann's message of "Fri, 15 Jan 2016 00:13 +0100")
Arnd Bergmann <arnd@arndb.de> writes:
> On Thursday 14 January 2016 08:46:29 Kalle Valo wrote:
>> I can take it. For historical reasons ssb patches go through my
>> wireless-drivers trees.
>
> I found this in my backlog, and I believe it still applies. Can you take
> that one too?
I'm not sure what you mean here, I can take any ssb patch if it's ok for
Michael or Rafal :)
Just please submit the patch properly (with S-o-B line) and CC
linux-wireless so that it goes to patchwork.
--
Kalle Valo
next prev parent reply other threads:[~2016-01-16 12:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 22:51 [PATCH] ssb: host_soc depends on sprom Arnd Bergmann
2016-01-14 6:46 ` Kalle Valo
2016-01-14 21:46 ` David Miller
2016-01-14 23:13 ` [PATCH, RESEND] ssb: mark ssb_bus_register as __maybe_unused Arnd Bergmann
2016-01-16 12:10 ` Kalle Valo [this message]
2016-01-16 14:44 ` Rafał Miłecki
2016-01-18 8:26 ` Kalle Valo
2016-01-18 16:53 ` ssb: Set linux-wireless as MAINTAINERS list Michael Büsch
2016-01-18 19:09 ` Rafał Miłecki
2016-01-19 13:04 ` Kalle Valo
2016-01-19 19:25 ` Kalle Valo
2016-01-18 19:39 ` [PATCH, RESEND^2] ssb: mark ssb_bus_register as __maybe_unused Arnd Bergmann
2016-01-19 13:03 ` Kalle Valo
2016-01-19 19:26 ` [RESEND^2] " Kalle Valo
2016-01-14 8:45 ` [PATCH] ssb: host_soc depends on sprom Rafał Miłecki
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=87bn8l7miw.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arnd@arndb.de \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=m@bues.ch \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox