From: Greg KH <greg@kroah.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Arend van Spriel" <arend@broadcom.com>,
"Michael Büsch" <mb@bu3sch.de>,
"Brett Rudley" <brudley@broadcom.com>,
"Henry Ptasinski" <henryp@broadcom.com>,
"John Linville" <linville@tuxdriver.com>,
"George Kashperko" <george@znau.edu.ua>,
linux-wireless@vger.kernel.org
Subject: Re: new utility kernel module for detecting cores in newer chipsets
Date: Mon, 21 Mar 2011 07:46:03 -0700 [thread overview]
Message-ID: <20110321144603.GA7645@kroah.com> (raw)
In-Reply-To: <AANLkTi=1eGo7uvP8Uy32yQezhGJTHYkHpEyX9vF=PujF@mail.gmail.com>
On Mon, Mar 21, 2011 at 03:27:49PM +0100, Rafał Miłecki wrote:
> 2011/3/21 Greg KH <greg@kroah.com>:
> > On Mon, Mar 21, 2011 at 11:12:55AM +0100, Rafał Miłecki wrote:
> >> Sorry, but you seem to be deaf to my and George's comments.
> >
> > Me?
> >
> >> What's wrong with that?
> >
> > What's wrong with what? You provided no context in this message, so I
> > have absolutely no idea what you are referring to.
> >
> > totally confused,
>
> Did you receive two following e-mails (in this thread):
> 1) From: Rafał Miłecki <zajec5@gmail.com>
> Date: 20 03 2011 10:55
> 2) From: George Kashperko <george@znau.edu.ua>
> Date: 20 03 2011 14:07
> ?
In digging through my archives, yes I did.
But the proper thing to do is to quote portions in which you refer to
when talking about them. Otherwise the reciever can easily be lost.
Remember, some of us get _thousands_ of emails a day. Remembering
context based on a subject: line is impossible, especially when the
thread is long gone from my inbox and buried in my archive.
> The case is, we discussed ssb/ai driver layout few days ago. George
> shared idea of layout I agree with, nobody shared any objections. If
> everything goes fine, we should have nicely modularized driver/project
> supporting Broadcom's buses.
>
> In this situation I'm not really interested is simple ai driver
> stripped from brcm80211. According to me, it would led to harder
> maintenance and harder implementation of support for such a driver in
> b43.
Ok, and I trust that you and Michael will work things out.
I have no objections to what you want at all, why do you think I do?
I'm just handling getting the stuff in drivers/staging/ out of there,
that's it. I trust the rest of you all to handle the design decisions
properly.
And as there is no code here yet to complain about, I fail to see any
problem yet :)
thanks,
greg k-h
next prev parent reply other threads:[~2011-03-21 14:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <op.vslagcb13ri7v4@arend-laptop>
2011-03-19 12:13 ` new utility kernel module for detecting cores in newer chipsets Arend van Spriel
2011-03-20 9:55 ` Rafał Miłecki
2011-03-20 13:07 ` George Kashperko
2011-03-20 17:04 ` Arend van Spriel
[not found] ` <1300538338.11949.12.camel@maggie>
[not found] ` <20110319214234.GA5152@kroah.com>
[not found] ` <1300573336.11949.25.camel@maggie>
[not found] ` <20110319234524.GA7493@kroah.com>
[not found] ` <op.vsmyhmei3ri7v4@arend-laptop>
[not found] ` <20110320145421.GA13962@kroah.com>
[not found] ` <op.vsnd1a1i3ri7v4@arend-laptop>
[not found] ` <20110320162200.GA17030@kroah.com>
[not found] ` <op.vsng7q1j3ri7v4@arend-laptop>
[not found] ` <20110320185216.GD19375@kroah.com>
2011-03-21 10:12 ` Rafał Miłecki
2011-03-21 14:05 ` Greg KH
2011-03-21 14:27 ` Rafał Miłecki
2011-03-21 14:46 ` Greg KH [this message]
2011-03-21 14:52 ` Rafał Miłecki
2011-03-21 15:16 ` Greg KH
2011-03-21 15:33 ` Rafał Miłecki
2011-03-21 15:05 ` Arend van Spriel
2011-03-21 15:14 ` John W. Linville
2011-03-21 15:30 ` Rafał Miłecki
2011-03-21 16:25 ` George Kashperko
2011-03-21 16:24 ` Michael Büsch
2011-03-21 16:28 ` Michael Büsch
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=20110321144603.GA7645@kroah.com \
--to=greg@kroah.com \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=george@znau.edu.ua \
--cc=henryp@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 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).