From: "Arend van Spriel" <arend@broadcom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Michael Büsch" <m@bues.ch>, "Rafał Miłecki" <zajec5@gmail.com>,
"Michael Buesch" <mb@bu3sch.de>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Greg KH" <greg@kroah.com>
Subject: Re: [PATCH] drivers: bcma: export bcma_core_disable() function
Date: Fri, 10 Jun 2011 18:29:57 +0200 [thread overview]
Message-ID: <4DF24685.3080702@broadcom.com> (raw)
In-Reply-To: <20110610134016.GC2665@tuxdriver.com>
On 06/10/2011 03:40 PM, John W. Linville wrote:
> On Fri, Jun 10, 2011 at 01:39:11PM +0000, Michael Büsch wrote:
>> On Fri, 10 Jun 2011 13:46:52 +0200
>> "Arend van Spriel"<arend@broadcom.com> wrote:
>>>> Michael said we should not do do such a exporting without getting
>>>> users within the same patch serie.
>>> That is going to be hard for me despite my willingness to comply. Our
>>> driver is still in staging so we submit our brcm80211 patches to Greg
>>> KH. I figured it would be better to do submit patches for bcma on
>>> wireless repository.
>> There are no rules without exceptions ;-)
> Right, so I don't really mind taking it. OTOH, maybe Greg could just
> carry the patch in his staging tree...?
>
> John
Thanks, John
I leave it up to Rafał and Michael to decide. Both ways are fine by me.
Gr. AvS
--
Almost nobody dances sober, unless they happen to be insane.
-- H.P. Lovecraft --
next prev parent reply other threads:[~2011-06-10 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 18:07 [PATCH] drivers: bcma: export bcma_core_disable() function Arend van Spriel
2011-06-10 11:40 ` Rafał Miłecki
2011-06-10 11:46 ` Arend van Spriel
2011-06-10 13:39 ` Michael Büsch
2011-06-10 13:40 ` John W. Linville
2011-06-10 16:29 ` Arend van Spriel [this message]
2011-06-10 17:19 ` Rafał Miłecki
2011-06-13 15:29 ` [PATCH] bcma: clean exports of functions 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=4DF24685.3080702@broadcom.com \
--to=arend@broadcom.com \
--cc=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=m@bues.ch \
--cc=mb@bu3sch.de \
--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.