From: Alexey Dobriyan <adobriyan@gmail.com>
To: Jerome Marchand <jmarchan@redhat.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Miklos Szeredi <mszeredi@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] procfs: fix tid fdinfo
Date: Sat, 24 Apr 2010 19:28:57 +0300 [thread overview]
Message-ID: <20100424162857.GB4428@x200> (raw)
In-Reply-To: <4BD1BF57.7070201@redhat.com>
On Fri, Apr 23, 2010 at 05:40:07PM +0200, Jerome Marchand wrote:
> - DIR("fdinfo", S_IRUSR|S_IXUSR, proc_fdinfo_inode_operations, proc_fd_operations),
> + DIR("fdinfo", S_IRUSR|S_IXUSR, proc_fdinfo_inode_operations, proc_fdinfo_operations),
Ick.
this is for stable@ as well
Cc: stable@kernel.org
prev parent reply other threads:[~2010-04-23 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 15:40 [PATCH] procfs: fix tid fdinfo Jerome Marchand
2010-04-23 18:16 ` Andrew Morton
2010-04-24 19:27 ` Alexey Dobriyan
2010-04-23 20:07 ` Miklos Szeredi
2010-04-26 7:49 ` Jerome Marchand
2010-04-26 10:26 ` Miklos Szeredi
2010-04-24 16:28 ` Alexey Dobriyan [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=20100424162857.GB4428@x200 \
--to=adobriyan@gmail.com \
--cc=jmarchan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=viro@zeniv.linux.org.uk \
/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