From: Michael Buesch <mb@bu3sch.de>
To: Ulrich Drepper <drepper@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] V2: O_CLOEXEC for SCM_RIGHTS
Date: Sun, 3 Jun 2007 00:14:50 +0200 [thread overview]
Message-ID: <200706030014.50305.mb@bu3sch.de> (raw)
In-Reply-To: <200706022148.l52LmVRx023291@devserv.devel.redhat.com>
On Saturday 02 June 2007 23:48:31 Ulrich Drepper wrote:
> Take two: I forgot to change the compat code. This has now happened. Only one
> additional line changed.
>
> Everything else from the first patch remains the same. I try to avoid clogging
> the list unnecessarily by not resending the test program.
>
>
> Signed-off-by: Ulrich Drepper <drepper@redhat.com>
>
> --- a/fs/open.c
> +++ b/fs/open.c
> @@ -855,7 +855,7 @@
> /*
> * Find an empty file descriptor entry, and mark it busy.
> */
> -static int get_unused_fd_flags(int flags)
> +int get_unused_fd_flags(int flags)
> {
> struct files_struct * files = current->files;
> int fd, error;
> --- a/include/linux/file.h
> +++ b/include/linux/file.h
> @@ -73,6 +73,7 @@ extern struct file * FASTCALL(fget_light(unsigned int fd, int *fput_needed));
> extern void FASTCALL(set_close_on_exec(unsigned int fd, int flag));
> extern void put_filp(struct file *);
> extern int get_unused_fd(void);
> +extern int FASTCALL(get_unused_fd_flags(int flags));
If you use FASTCALL macro here, you must use fastcall macro at
the definition above, too.
--
Greetings Michael.
prev parent reply other threads:[~2007-06-02 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 21:48 [PATCH] V2: O_CLOEXEC for SCM_RIGHTS Ulrich Drepper
2007-06-02 22:14 ` Michael Buesch [this message]
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=200706030014.50305.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).