All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Grant Coady <gcoady.lk@gmail.com>
Cc: mtosatti@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.33-rc3 needs to export memchr() for smbfs
Date: Thu, 3 Aug 2006 04:40:37 +0200	[thread overview]
Message-ID: <20060803024037.GB18264@1wt.eu> (raw)
In-Reply-To: <27i2d214opklm6aa6hglfo1c45sp45cmf0@4ax.com>

On Thu, Aug 03, 2006 at 11:21:51AM +1000, Grant Coady wrote:
> On Wed, 2 Aug 2006 23:46:08 +0200, Willy Tarreau <w@1wt.eu> wrote:
> 
> >Hi Marcelo,
> >
> >just finished building 2.4.33-rc3 on my dual-CPU Sun U60 (works
> >fine BTW). I noticed that smbfs built as a module needs memchr()
> >since a recent fix, so this one now needs to be exported, which
> >this patch does.  Sources show that the lp driver would need it
> >too is console on LP is enabled and LP is set as a module (which
> >seems stupid to me anyway). I've pushed it into -upstream if you
> >prefer to pull from it.
> >
> >Overall, 2.4.33-rc3 seems to be OK to me. I don't think that
> >an additionnal -rc4 would be needed just for this export (Grant
> >CCed in case he's wishing to do a few more builds, you know
> >him...  :-) ).
> 
> Just one build, deltree server 'cos it exports some shares to 'doze 
> boxen.  Seems to be okay without the patch but...
>
> Makes no difference to my limited usage here.  Didn't break ;)

Interesting, I wonder whether memchr() may be a gcc builtin on some
archs, explaining why it works without the patch on your machine.

> <http://bugsplatter.mine.nu/test/boxen/deltree/> *-rc3a
> 
> uptime 21 mins...

Thanks very much, that's exactly what I needed.

> Cheers,
> Grant.

Cheers,
Willy


  reply	other threads:[~2006-08-03  2:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02 21:46 [PATCH] 2.4.33-rc3 needs to export memchr() for smbfs Willy Tarreau
2006-08-03  1:21 ` Grant Coady
2006-08-03  2:40   ` Willy Tarreau [this message]
2006-08-03  3:26     ` Grant Coady
2006-08-03  4:24       ` Willy Tarreau

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=20060803024037.GB18264@1wt.eu \
    --to=w@1wt.eu \
    --cc=gcoady.lk@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.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.