* [patch] iw: align output for HT capabilities
@ 2009-02-03 0:10 pat-lkml
2009-02-03 0:15 ` Julian Calaby
0 siblings, 1 reply; 3+ messages in thread
From: pat-lkml @ 2009-02-03 0:10 UTC (permalink / raw)
To: linux-wireless
The HT capabilities have an additional space in front of them causing
them not to line up with the rest of the listed outputs. This patch
removes that space.
Signed-off-by: Pat Erley <pat-lkml@erley.org>
---
diff --git a/info.c b/info.c
index bf3b8bd..69be500 100644
--- a/info.c
+++ b/info.c
@@ -70,7 +70,7 @@ static int print_phy_handler(struct nl_msg *msg, void
*arg)
#ifdef NL80211_BAND_ATTR_HT_CAPA
if (tb_band[NL80211_BAND_ATTR_HT_CAPA]) {
unsigned short cap = nla_get_u16(tb_band[NL80211_BAND_ATTR_HT_CAPA]);
-#define PCOM(fmt, args...) do { printf("\t\t\t * " fmt "\n", ##args); }
while (0)
+#define PCOM(fmt, args...) do { printf("\t\t\t* " fmt "\n", ##args); }
while (0)
#define PBCOM(bit, args...) if (cap & (bit)) PCOM(args)
printf("\t\tHT capabilities: 0x%.4x\n", cap);
PBCOM(0x0001, "LPDC coding");
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [patch] iw: align output for HT capabilities
2009-02-03 0:10 [patch] iw: align output for HT capabilities pat-lkml
@ 2009-02-03 0:15 ` Julian Calaby
2009-02-03 0:18 ` pat-lkml
0 siblings, 1 reply; 3+ messages in thread
From: Julian Calaby @ 2009-02-03 0:15 UTC (permalink / raw)
To: pat-lkml; +Cc: linux-wireless
On Tue, Feb 3, 2009 at 11:10, pat-lkml <pat-lkml@erley.org> wrote:
> The HT capabilities have an additional space in front of them causing
> them not to line up with the rest of the listed outputs. This patch
> removes that space.
>
> Signed-off-by: Pat Erley <pat-lkml@erley.org>
>
> ---
>
> diff --git a/info.c b/info.c
> index bf3b8bd..69be500 100644
> --- a/info.c
> +++ b/info.c
> @@ -70,7 +70,7 @@ static int print_phy_handler(struct nl_msg *msg, void
> *arg)
> #ifdef NL80211_BAND_ATTR_HT_CAPA
> if (tb_band[NL80211_BAND_ATTR_HT_CAPA]) {
> unsigned short cap = nla_get_u16(tb_band[NL80211_BAND_ATTR_HT_CAPA]);
> -#define PCOM(fmt, args...) do { printf("\t\t\t * " fmt "\n", ##args); }
> while (0)
> +#define PCOM(fmt, args...) do { printf("\t\t\t* " fmt "\n", ##args); }
> while (0)
Is it just me or is this patch line-wrapped?
Thanks,
--
Julian Calaby
Email: julian.calaby@gmail.com
.Plan: http://sites.google.com/site/juliancalaby/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [patch] iw: align output for HT capabilities
2009-02-03 0:15 ` Julian Calaby
@ 2009-02-03 0:18 ` pat-lkml
0 siblings, 0 replies; 3+ messages in thread
From: pat-lkml @ 2009-02-03 0:18 UTC (permalink / raw)
To: Julian Calaby; +Cc: linux-wireless
Julian Calaby wrote:
> On Tue, Feb 3, 2009 at 11:10, pat-lkml <pat-lkml@erley.org> wrote:
>> The HT capabilities have an additional space in front of them causing
>> them not to line up with the rest of the listed outputs. This patch
>> removes that space.
>>
>> Signed-off-by: Pat Erley <pat-lkml@erley.org>
>>
>> ---
>>
>> diff --git a/info.c b/info.c
>> index bf3b8bd..69be500 100644
>> --- a/info.c
>> +++ b/info.c
>> @@ -70,7 +70,7 @@ static int print_phy_handler(struct nl_msg *msg, void
>> *arg)
>> #ifdef NL80211_BAND_ATTR_HT_CAPA
>> if (tb_band[NL80211_BAND_ATTR_HT_CAPA]) {
>> unsigned short cap = nla_get_u16(tb_band[NL80211_BAND_ATTR_HT_CAPA]);
>> -#define PCOM(fmt, args...) do { printf("\t\t\t * " fmt "\n", ##args); }
>> while (0)
>> +#define PCOM(fmt, args...) do { printf("\t\t\t* " fmt "\n", ##args); }
>> while (0)
>
> Is it just me or is this patch line-wrapped?
>
> Thanks,
>
no, it line wrapped. Weird that it'd line wrap the function def but not
the line later on me, but I guess it's time to look into fixing my mail
client.
Thanks,
Pat
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-02-03 0:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-03 0:10 [patch] iw: align output for HT capabilities pat-lkml
2009-02-03 0:15 ` Julian Calaby
2009-02-03 0:18 ` pat-lkml
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).