All of lore.kernel.org
 help / color / mirror / Atom feed
From: "George Spelvin" <linux@sciencehorizons.net>
To: bfields@fieldses.org, linux@horizon.com, linux@sciencehorizons.net
Cc: jlayton@poochiereds.net, linux-nfs@vger.kernel.org
Subject: Re: [PATCH RESEND 03/10] <linux/sunrpc/svcauth.h>: Define hash_str() in terms of hash_string()
Date: 26 May 2016 23:29:46 -0400	[thread overview]
Message-ID: <20160527032946.12751.qmail@ns.sciencehorizons.net> (raw)
In-Reply-To: <20160527015605.7083.qmail@ns.sciencehorizons.net>

Okay, it's now okay to re-pull.  I renamed mine to hashlen_string(),
since that's what it returns (the hash and the length), which both
solves the problem,and is frankly a better name.

Thank you for prodding me to wade through the GCC 6 warning
spam.  Thre were some problems hiding there.

I discovered that adding #include <linux/bug.h> breaks the tools.perf
build.  It makes local copies of some kernel headers under control of
a MANIFEST file, and I can't be arsed to figure it out.

So I deleted the BUILD_BUG_ON entirely, and it's now (finally!) finished
an allyesconfig build without any warnings that look new.

  reply	other threads:[~2016-05-27  3:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160527003254.GA25272@fieldses.org>
2016-05-27  1:56 ` [PATCH RESEND 03/10] <linux/sunrpc/svcauth.h>: Define hash_str() in terms of hash_string() George Spelvin
2016-05-27  3:29   ` George Spelvin [this message]
2016-05-27 12:16     ` J. Bruce Fields
2016-05-27 12:20       ` George Spelvin
2016-05-27 17:40         ` J. Bruce Fields
2016-05-27 21:25           ` George Spelvin
2016-05-27 17:14       ` I may be on the trail of that bug you hit George Spelvin
2016-05-25  7:26 [PATCH 03/10] <linux/sunrpc/svcauth.h>: Define hash_str() in terms of hash_string() George Spelvin
2016-05-26 18:39 ` [PATCH RESEND " George Spelvin
2016-05-26 18:45   ` J. Bruce Fields

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=20160527032946.12751.qmail@ns.sciencehorizons.net \
    --to=linux@sciencehorizons.net \
    --cc=bfields@fieldses.org \
    --cc=jlayton@poochiereds.net \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux@horizon.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 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.