From: David Miller <davem@davemloft•net>
To: jlayton@redhat•com
Cc: sfr@canb•auug.org.au, smfrench@gmail•com,
linux-cifs-client@lists•samba.org, linux-next@vger•kernel.org,
harvey.harrison@gmail•com
Subject: Re: linux-next: cifs tree build failure
Date: Wed, 03 Dec 2008 12:40:34 -0800 (PST) [thread overview]
Message-ID: <20081203.124034.142747347.davem@davemloft.net> (raw)
In-Reply-To: <20081203065721.1b68a5a1@tleilax.poochiereds.net>
From: Jeff Layton <jlayton@redhat•com>
Date: Wed, 3 Dec 2008 06:57:21 -0500
> Still, is there some reason that NIP6/NIPQUAD stuff needs to be removed
> at the same time as we add %pI4/%pI6? An period where the old NIP*
> defines still live in the tree seems like a reasonable thing.
Actually, from my perspective, killing the macros turns out to
be a good thing. It caught a potential revert of the conversion
we did in CIFS already, for example :)
Unlike a compile failure, we don't have some automated thing
scanning new patches looking for references to turds like these
NIPQUAD macros which we want to remove.
next prev parent reply other threads:[~2008-12-03 20:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 2:23 linux-next: cifs tree build failure Stephen Rothwell
2008-12-03 2:53 ` Stephen Rothwell
2008-12-03 3:19 ` David Miller
2008-12-03 11:57 ` Jeff Layton
2008-12-03 20:40 ` David Miller [this message]
2008-12-12 3:32 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-02-24 6:56 Stephen Rothwell
2009-02-24 14:45 ` Steve French
2009-02-25 3:03 ` Stephen Rothwell
2009-04-03 2:07 Stephen Rothwell
2009-04-03 3:31 Steve French
2009-04-14 1:41 Stephen Rothwell
2009-04-15 2:59 ` Stephen Rothwell
2009-04-15 3:10 ` Steve French
2009-04-15 3:20 ` Stephen Rothwell
2009-06-15 3:32 Stephen Rothwell
2009-06-15 10:46 ` Jeff Layton
2009-06-15 13:47 ` Steve French
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=20081203.124034.142747347.davem@davemloft.net \
--to=davem@davemloft$(echo .)net \
--cc=harvey.harrison@gmail$(echo .)com \
--cc=jlayton@redhat$(echo .)com \
--cc=linux-cifs-client@lists$(echo .)samba.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=smfrench@gmail$(echo .)com \
/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