mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Namesys.COM>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiser4 breaks vmware
Date: Thu, 25 Dec 2003 12:29:15 +0300	[thread overview]
Message-ID: <16362.44523.653063.676562@laputa.namesys.com> (raw)
In-Reply-To: <p73pted2772.fsf@verdi.suse.de>

Andi Kleen writes:
 > Nikita Danilov <Nikita@Namesys.COM> writes:
 > 
 > > Exactly. I included it into core.diff by mistake.
 > > Revert it: http://www.namesys.com/snapshots/2003.12.23/broken-out/do_mmap2-fix.diff.patch
 > 
 > There seem to be some other unnecessary patches in there, like
 > init_fixmap_vma.diff.patch. I cannot imagine why a file system should

Yes, UML left-over also, thank you for noting.

 > need to change that. Same with spinlock-owner.diff.patch. Is that
 > really needed? If yes porting it to all architectures will be a lot of

No, it is debugging code, and I think it is reasonably to ship it
together with reiser4 while it is in the debugging stage. Debugging
patches are going to be removed eventually.

 > work.
 > 
 > I would suggest separating your debug patches, like page-owner.diff.patch
 > 
 > And your webserver is misconfigured: I thinks READ.ME is a troff
 > document.

Hmm. This was fixed long time ago.

$ telnet namesys.com 80
Trying 212.16.7.65...
Connected to thebsh.namesys.com (212.16.7.65).
Escape character is '^]'.
GET /snapshots/2003.12.23/READ.ME HTTP/1.0

HTTP/1.1 200 OK
Date: Thu, 25 Dec 2003 09:20:45 GMT
Server: Apache/1.3.23 (Unix)  (Red-Hat/Linux)
Last-Modified: Tue, 23 Dec 2003 11:31:22 GMT
ETag: "e3b05-fab-3fe8278a"
Accept-Ranges: bytes
Content-Length: 4011
Connection: close
Content-Type: text/plain

 > 
 > The other changes look reasonable, although a lot of the EXPORT_SYMBOLs
 > should be probably EXPORT_SYMBOL_GPL and carry some more comments about

What are the guidelines for using EXPORT_SYMBOL vs. EXPORT_SYMBOL_GPL?

 > their purpose.
 > 
 > -Andi

Nikita.

  reply	other threads:[~2003-12-25  9:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1072202167.8127.15.camel@localhost.suse.lists.linux.kernel>
     [not found] ` <3FE8B765.6000907@vgertech.com.suse.lists.linux.kernel>
     [not found]   ` <16361.18888.602000.438746@laputa.namesys.com.suse.lists.linux.kernel>
2003-12-24 22:15     ` Andi Kleen
2003-12-25  9:29       ` Nikita Danilov [this message]
2003-12-23 17:56 Shawn
2003-12-23 19:21 ` Hans Reiser
2003-12-23 21:45 ` Nuno Silva
2003-12-24  8:09   ` Nikita Danilov

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=16362.44523.653063.676562@laputa.namesys.com \
    --to=nikita@namesys.com \
    --cc=ak@suse.de \
    --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

Powered by JetHome