public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	"linux-arm-kernel\@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-mips\@linux-mips.org" <linux-mips@linux-mips.org>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michael Buesch <m@bues.ch>,
	Network Development <netdev@vger.kernel.org>
Subject: Re: [PATCH, RESEND] ssb: mark ssb_bus_register as __maybe_unused
Date: Mon, 18 Jan 2016 10:26:29 +0200	[thread overview]
Message-ID: <87y4bn5m4q.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CACna6ryvDFHqwJ3ExURcyFT2ZaT9fS9v36wCnJfze5BLnE88og@mail.gmail.com> ("Rafał Miłecki"'s message of "Sat, 16 Jan 2016 15:44:23 +0100")

Rafał Miłecki <zajec5@gmail.com> writes:

> On 16 January 2016 at 13:10, Kalle Valo <kvalo@codeaurora.org> wrote:
>> 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.
>
> It was already sent once and Acked by Michael:
> https://patchwork.kernel.org/patch/7543191/
>
> The problem was not cc-ing linux-wireless so it wasn't picked by the
> linux-wireless patchwork.

Ah, that's why I missed it. I only follow patchwork, I basically ignore
patches which are sent via email. Arnd, can you please resend the patch
and CC linux-wireless? Sorry for the trouble.

To avoid this in the future I think we should replace netdev with
linux-wireless in the MAINTAINERS entry:

SONICS SILICON BACKPLANE DRIVER (SSB)
M:      Michael Buesch <m@bues.ch>
L:      netdev@vger.kernel.org
S:      Maintained
F:      drivers/ssb/
F:      include/linux/ssb/

Are people ok with that? Patches welcome :)

-- 
Kalle Valo

  reply	other threads:[~2016-01-18  8:26 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
2016-01-16 14:44       ` Rafał Miłecki
2016-01-18  8:26         ` Kalle Valo [this message]
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=87y4bn5m4q.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