From: Alistair John Strachan <alistair@devzero.co.uk>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH/RFC] Merge ath9k_txq_info and ath9k_tx_queue_info (was Re: New TODO - 2008-08-04)
Date: Wed, 6 Aug 2008 17:20:00 +0100 [thread overview]
Message-ID: <200808061720.00612.alistair@devzero.co.uk> (raw)
Hi Luis,
(Sorry for not replying in the thread but I subscribed to the list after you'd
posted it.)
I've just finished one of the "Cleanup" aspects:
"Merge ath9k_txq_info and ath9k_tx_queue_info."
For the moment I went with ath9k_tx_queue_info, because this is more
consistent with the names of other ath9k_tx_queue_XXX structures. However, it
results in more churn. The patch is attached.
Which name do you prefer? I'll rework the patch for the other one, if you'd
like. Either way I'll resend with sign-offs, inline, et al. if this work is
still useful.
Compile and runtime tested.
--
Cheers,
Alistair.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ath9k-remove-struct-ath9k_txq_info.diff
Type: text/x-patch
Size: 7881 bytes
Desc: not available
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20080806/11c0c79c/attachment.bin
reply other threads:[~2008-08-06 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200808061720.00612.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=ath9k-devel@lists.ath9k.org \
/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.