From: "Kristian Sørensen" <ks@cs.auc.dk>
To: Martin Zwickel <martin.zwickel@technotrend.de>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why dentry->d_qstr change in 2.6.7 ?
Date: Wed, 23 Jun 2004 16:23:54 +0200 [thread overview]
Message-ID: <1088000634.10861.5.camel@localhost> (raw)
In-Reply-To: <20040623161557.6814a3ae@phoebee>
Thanks for the link. That was indeed the information I was looking for
:)
On Wed, 2004-06-23 at 16:15, Martin Zwickel wrote:
> On Wed, 23 Jun 2004 16:04:29 +0200
> Kristian Sørensen <ks@cs.auc.dk> bubbled:
>
> > Can it really be, that noone knows why this change has been made !??
>
> maybe this is for your interest:
> http://lkml.org/lkml/2004/5/8/20
--
Kristian Sørensen <ks@cs.auc.dk>
prev parent reply other threads:[~2004-06-23 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 15:51 Why dentry->d_qstr change in 2.6.7 ? Kristian Sørensen
2004-06-23 14:04 ` Kristian Sørensen
2004-06-23 14:10 ` Christoph Hellwig
2004-06-23 14:22 ` Kristian Sørensen
2004-06-23 20:55 ` Andrew Morton
2004-06-23 20:54 ` Christoph Hellwig
2004-06-23 14:15 ` Martin Zwickel
2004-06-23 14:23 ` Kristian Sørensen [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=1088000634.10861.5.camel@localhost \
--to=ks@cs.auc.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.zwickel@technotrend.de \
/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