From: Al Viro <viro@ftp.linux.org.uk>
To: Borislav Petkov <bbpetkov@yahoo.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
tgraf@suug.ch, pablo@eurodev.net
Subject: Re: [was: Linux v2.6.14-rc4] fix textsearch build warning
Date: Tue, 11 Oct 2005 21:59:49 +0100 [thread overview]
Message-ID: <20051011205949.GU7992@ftp.linux.org.uk> (raw)
In-Reply-To: <20051011145454.GA30786@gollum.tnic>
On Tue, Oct 11, 2005 at 04:54:54PM +0200, Borislav Petkov wrote:
> I get this when building 14-rc4:
>
> lib/ts_kmp.c:125: warning: initialization from incompatible pointer type
> lib/ts_bm.c:165: warning: initialization from incompatible pointer type
> lib/ts_fsm.c:318: warning: initialization from incompatible pointer type
>
> The following trivial patch fixes it.
Umm... I'd rather get all that stuff dealt with in one go - I've got gfp_t
conversion finished and it's waiting for 2.6.14.
Fix for that one had been sent, actually - see part 4 of gfp_t annotations
series. Since none of that stuff is critical (the only bug caught so far
had been already fixed - see relayfs patch) and Linus decided to go for
2.6.14-final, let's hold it back and merge as soon as 2.6.14 gets released.
next prev parent reply other threads:[~2005-10-11 20:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 1:31 Linux v2.6.14-rc4 Linus Torvalds
2005-10-11 3:41 ` Al Viro
2005-10-11 3:58 ` David S. Miller
2005-10-11 4:24 ` Al Viro
2005-10-11 4:40 ` David S. Miller
2005-10-11 14:54 ` [was: Linux v2.6.14-rc4] fix textsearch build warning Borislav Petkov
2005-10-11 20:59 ` Al Viro [this message]
2005-10-11 23:02 ` Borislav Petkov
2005-10-11 23:24 ` Al Viro
2005-10-11 23:33 ` Linus Torvalds
2005-10-11 23:38 ` Linus Torvalds
2005-10-11 23:49 ` Al Viro
2005-10-12 0:57 ` Linus Torvalds
2005-10-12 8:27 ` Borislav Petkov
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=20051011205949.GU7992@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=bbpetkov@yahoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pablo@eurodev.net \
--cc=tgraf@suug.ch \
--cc=torvalds@osdl.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.