From: Dan Williams <dcbw@redhat.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org, libertas-dev@lists.infradead.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH, take 2] libertas: convert GET_LOG to a direct command
Date: Thu, 13 Mar 2008 11:23:32 -0400 [thread overview]
Message-ID: <1205421812.25425.2.camel@localhost.localdomain> (raw)
In-Reply-To: <200803131604.54033.hs4233@mail.mn-solutions.de>
On Thu, 2008-03-13 at 16:04 +0100, Holger Schurig wrote:
> > Sound OK?
>
> Generally ok. Do you want this in "incremental" style, as a patch
> on top of this one? Or do you want a more radical patch
> replacing this one ?
Either way, fine by me. If you send an incremental one, I'll ack both.
If you send a combined new patch, I'll ack that ;)
Dan
next prev parent reply other threads:[~2008-03-13 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 9:10 [PATCH, take 2] libertas: convert GET_LOG to a direct command Holger Schurig
2008-03-13 14:37 ` Dan Williams
2008-03-13 15:04 ` Holger Schurig
2008-03-13 15:23 ` Dan Williams [this message]
2008-03-17 11:45 ` Holger Schurig
2008-03-17 21:32 ` Dan Williams
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=1205421812.25425.2.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).