public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: wireless <linux-wireless@vger.kernel.org>,
	b43-dev <b43-dev@lists.infradead.org>,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: [PATCH] Add uevent to bcma bus, to autoload drivers.
Date: Thu, 18 Aug 2011 08:51:36 +0100	[thread overview]
Message-ID: <1313653897.13224.4.camel@shinybook.infradead.org> (raw)
In-Reply-To: <CACna6rzQmEE-EF+7tvQ8vkwp9bYwWMkna3UHw8ym7PmjKWWQTQ@mail.gmail.com>

On Thu, 2011-08-18 at 08:46 +0200, Rafa? Mi?ecki wrote:
> 
> Tested on my BCM43224, thanks a lot! :)
> 
> Acked-by: Rafa? Mi?ecki <zajec5@gmail.com>
> 
> You didn't send this directly to John, not sure if he will pick it up.
> 
> Do you think this should go for 3.1? With this patch ppl will directly
> see interface is present and will just use it or see error about
> firmware in dmesg. Without the patch, person just have to know b43 is
> supposed to support his card. 

Yes, it should go in for 3.1.

I wasn't really expecting John to pick it up. You are the maintainer of
drivers/bcma, so I'd expect to send it to *you*. Many maintainers would
be unhappy at patches being sent upstream and bypassing them. Normally
I'd expect you to pick up the patch and add it to your tree/queue with
your own signed-off-by, and for it to go upstream that way.

Of course, I'm happy to send it on directly if that's what you prefer.

-- 
dwmw2

  reply	other threads:[~2011-08-18  7:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-30 15:19 Report on bcma with 14e4:4353 (BCM43224) Larry Finger
2011-08-17 18:27 ` Rafał Miłecki
2011-08-17 21:43   ` [PATCH] Add uevent to bcma bus, to autoload drivers David Woodhouse
2011-08-18  6:46     ` Rafał Miłecki
2011-08-18  7:51       ` David Woodhouse [this message]
2011-08-19 20:13         ` Rafał Miłecki
2011-08-19 20:52           ` David Woodhouse
2011-08-19 21:17             ` 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=1313653897.13224.4.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@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