From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linville@tuxdriver.com, arnd@arndnet.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH][RESEND] ath9k: Fix ath_print in xmit for hardware reset.
Date: Wed, 26 May 2010 11:34:10 -0700 [thread overview]
Message-ID: <4BFD69A2.2040808@gmail.com> (raw)
In-Reply-To: <AANLkTinjgtKhQJ1UoQPY8aUFxhb3qrKrYjBgAZz1asZ_@mail.gmail.com>
On 05/26/2010 11:14 AM, Luis R. Rodriguez wrote:
> On Wed, May 26, 2010 at 11:12 AM, Justin P. Mattock
> <justinmattock@gmail.com> wrote:
>
>> On 05/26/2010 11:09 AM, Luis R. Rodriguez wrote:
>>
>>> On Wed, May 26, 2010 at 11:07 AM, Justin P. Mattock
>>> <justinmattock@gmail.com> wrote:
>>>
>
>>>> what about all the signed-off's? should I
>>>> resend with all of those, or no?
>>>>
>>
>>> I do not get what you are asking.
>>>
>> all the people that gave there 00.02$ on this to
>> make it all-good
>>
> Heh... no. SOBs are just for the authors of the code. The real purpose
> of SOB is explained on Documentation/SubmittingPatches, read
> "Developer's Certificate of Origin 1.1".
>
> Luis
>
>
I thought you were talking about
Son of a bit*h(was like what's this guy
talkin about man!!
I'll read up today!!
Justin P. Mattock
prev parent reply other threads:[~2010-05-26 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 18:00 [PATCH][RESEND] ath9k: Fix ath_print in xmit for hardware reset Justin P. Mattock
2010-05-26 18:02 ` Luis R. Rodriguez
2010-05-26 18:07 ` Justin P. Mattock
2010-05-26 18:09 ` Luis R. Rodriguez
2010-05-26 18:12 ` Justin P. Mattock
2010-05-26 18:14 ` Luis R. Rodriguez
2010-05-26 18:34 ` Justin P. Mattock [this message]
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=4BFD69A2.2040808@gmail.com \
--to=justinmattock@gmail.com \
--cc=arnd@arndnet.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@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.