- Add configuration option for developmental write support with an
  appropriately scary configuration help text.
- Initial implementation of fs/ntfs/aops.c::ntfs_writepage() and its
  helper fs/ntfs/aops.c::ntfs_write_block(). This enables mmap(2) based
  overwriting of existing files on ntfs. Note: Resident files are
  only written into memory, and not written out to disk at present, so
  avoid writing to files smaller than about 1kiB.
- Initial implementation of fs/ntfs/aops.c::ntfs_prepare_write(), its
  helper fs/ntfs/aops.c::ntfs_prepare_nonresident_write() and their
  counterparts, fs/ntfs/aops.c::ntfs_commit_write(), and
  fs/ntfs/aops.c::ntfs_commit_nonresident_write(), respectively. Also,
  add generic_file_write() to the ntfs file operations (fs/ntfs/file.c).
  This enables write(2) based overwriting of existing files on ntfs.
  Note: As with mmap(2) based overwriting, resident files are only
  written into memory, and not written out to disk at present, so avoid
  writing to files smaller than about 1kiB.
- Implement ->truncate (fs/ntfs/inode.c::ntfs_truncate()) and
  ->setattr() (fs/ntfs/inode.c::ntfs_setattr()) inode operations for
  files with the purpose of intercepting and aborting all i_size
  changes which we do not support yet. ntfs_truncate() actually only
  emits a warning message but AFAICS our interception of i_size changes
  elsewhere means ntfs_truncate() never gets called for i_size changes.
  It is only called from generic_file_write() when we fail in
  ntfs_prepare_{,nonresident_}write() in order to discard any
  instantiated buffers beyond i_size. Thus i_size is not actually
  changed so our warning message is enough. Unfortunately it is not
  possible to easily determine if i_size is being changed or not hence
  we just emit an appropriately worded error message.

files on ntfs. (Note: Resident files are not supported yet, so avoid
writing to files smaller than 1kiB.)

Make sure that the VC tty pointer is cleared when the tty is free'd.

into home.transmeta.com:/home/torvalds/v2.5/linux

into samba.org:/scratch/anton/linux-2.5_ppc64drivers

into home.transmeta.com:/home/torvalds/v2.5/linux

into groveronline.com:/root/bk/linux-acpi

into groveronline.com:/root/bk/linux-acpi

into hostme.bitkeeper.com:/ua/repos/l/linux-acpi/linux-acpi

into home.transmeta.com:/home/torvalds/v2.5/linux

bit of cleaning later.

a bit later

Note: I've also fixed several obvious "forgot to update" problems (changed
prototype of blk_init_queue(), etc.) but I hadn't touched the DMA-mapping
stuff, so it still doesn't work with 2.5; moreover, it misses a lot of fixes
done in 2.4, but that's fun for Alan - he's the maintainer

into samba.org:/scratch/anton/linux-2.5_work

into samba.org:/scratch/anton/linux-2.5_work

into samba.org:/scratch/anton/linux-2.5_work

Well I didn't test that very well.  __page_cache_release() is doing a
__free_page() on a zero-ref page, so __free_pages() sends the refcount
negative and doesn't free it.  With patch #8, page_cache_release()
almost never frees pages, but it must have been leaking a little bit.
Lucky it showed up.

This fixes it, and also adds a missing PageReserved test in put_page().
Which makes put_page() identical to page_cache_release(), but there are
header file woes.  I'll fix that up later.

This trivial patch reorders the unlocking in rq_unlock()... I was
tired of getting stack dumps in my messages file.

isn't ready for it (either during early boot, or at shutdown)

into home.transmeta.com:/home/torvalds/v2.5/linux

Make sure to properly reset the state after disconnect

(Karsten Keil)

Newer gcc's don't like string concat with __FUNCTION__, so
use %s and __FUNCTION__ as argument.

Thanks to Rusty for posting the script...

drivers/isdn/hysdn/Config.in was referring to
CONFIG_ISDN_CAPI before it was defined.

Noticed by Greg Banks.