From: David Miller <davem@davemloft•net>
To: sfr@canb•auug.org.au
Cc: linux-next@vger•kernel.org, a.beregalov@gmail•com
Subject: Re: linux-next: net tree build warnings
Date: Wed, 29 Apr 2009 17:54:13 -0700 (PDT) [thread overview]
Message-ID: <20090429.175413.81058049.davem@davemloft.net> (raw)
In-Reply-To: <20090428.230232.113827653.davem@davemloft.net>
From: David Miller <davem@davemloft•net>
Date: Tue, 28 Apr 2009 23:02:32 -0700 (PDT)
> From: Stephen Rothwell <sfr@canb•auug.org.au>
> Date: Wed, 29 Apr 2009 14:59:21 +1000
>
>> Caused by commit 011983048a120e520147361be1067dd82343038e ("vxge: use max()
>> instead of VXGE_HW_SET_LEVEL").
>
> Maybe that's why the macro was used in the first place :-)
>
> We probably have to use something like max_t() here, and to me that's
> worse than the macro it is replacing.
Nobody is doing anything about this so I'm simply reverting.
next prev parent reply other threads:[~2009-04-30 0:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 4:59 linux-next: net tree build warnings Stephen Rothwell
2009-04-29 6:02 ` David Miller
2009-04-30 0:54 ` David Miller [this message]
2009-04-30 7:06 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-10-14 4:20 Stephen Rothwell
2009-10-14 4:34 ` Stephen Rothwell
2009-10-14 22:11 ` David Miller
2009-10-15 1:55 ` Arnaldo Carvalho de Melo
2009-09-04 4:34 Stephen Rothwell
2009-09-04 4:35 ` David Miller
2009-06-11 4:55 Stephen Rothwell
2009-06-11 6:47 ` David Miller
2009-06-11 7:20 ` Stephen Rothwell
2009-03-26 6:37 Stephen Rothwell
2009-03-26 7:50 ` Eric Leblond
2009-03-26 13:17 ` Patrick McHardy
2009-03-26 22:01 ` Stephen Rothwell
2009-03-16 6:03 Stephen Rothwell
2009-03-16 6:05 ` Dhananjay Phadke
2008-12-17 7:22 Stephen Rothwell
2008-12-17 7:53 ` David Miller
2008-12-17 8:04 ` Eilon Greenstein
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=20090429.175413.81058049.davem@davemloft.net \
--to=davem@davemloft$(echo .)net \
--cc=a.beregalov@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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