From: Manik Raina <manik@cisco.com>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] small compile warning fix
Date: Tue, 30 Oct 2001 09:53:41 +0530 [thread overview]
Message-ID: <3BDE2B4D.CA679FF1@cisco.com> (raw)
In-Reply-To: <7A9BC5E3241@vcnet.vc.cvut.cz>
Petr Vandrovec wrote:
> On 29 Oct 01 at 15:43, Manik Raina wrote:
> >
> > Index: ncplib_kernel.c
> > ===================================================================
> > RCS file: /vger/linux/fs/ncpfs/ncplib_kernel.c,v
> > retrieving revision 1.29
> > diff -u -r1.29 ncplib_kernel.c
> > --- ncplib_kernel.c 18 Sep 2001 22:29:08 -0000 1.29
> > +++ ncplib_kernel.c 29 Oct 2001 10:09:27 -0000
> > @@ -52,6 +52,11 @@
> > return;
> > }
> >
> > +#ifdef LATER
> > +/*
> > + * This function is not currently in use. This leads to a compiler warning.
> > + * Remove #ifdef when in use...
> > + */
> > static void ncp_add_mem_fromfs(struct ncp_server *server, const char *source, int size)
> > {
> > assert_server_locked(server);
>
> You can remove it completely. It should not be '#ifdef LATER', but
> '#ifdef OLDVERSION'... ncp_add_mem_fromfs was invoked with lock on
> ncp_server structure, but then it directly accessed userspace. It was
> possible to use this to cause deadlock, so now ncpfs uses bounce buffers
> and double copy instead of this.
>
would you include this in your patches or would you like me to make
it #ifdef OLDVERSION ?
thanks
Manik
>
> I have some ncpfs patches, but I though that I'll leave them for 2.5.x.
> Maybe it is time to change this decision.
> Best regards,
> Petr Vandrovec
> vandrove@vc.cvut.cz
>
next prev parent reply other threads:[~2001-10-30 4:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 16:13 [PATCH] small compile warning fix Petr Vandrovec
2001-10-30 4:23 ` Manik Raina [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-30 21:21 Petr Vandrovec
2001-10-29 10:13 Manik Raina
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=3BDE2B4D.CA679FF1@cisco.com \
--to=manik@cisco.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox