1. 10 7月, 2007 1 次提交
  2. 29 6月, 2007 3 次提交
  3. 25 4月, 2007 1 次提交
    • D
      [JFFS2] Tidy up licensing/copyright boilerplate. · c00c310e
      David Woodhouse 提交于
      In particular, remove the bit in the LICENCE file about contacting
      Red Hat for alternative arrangements. Their errant IS department broke
      that arrangement a long time ago -- the policy of collecting copyright
      assignments from contributors came to an end when the plug was pulled on
      the servers hosting the project, without notice or reason.
      
      We do still dual-license it for use with eCos, with the GPL+exception
      licence approved by the FSF as being GPL-compatible. It's just that nobody
      has the right to license it differently.
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      c00c310e
  4. 18 4月, 2007 1 次提交
  5. 27 6月, 2006 2 次提交
  6. 27 5月, 2006 1 次提交
  7. 25 5月, 2006 2 次提交
  8. 24 5月, 2006 1 次提交
    • D
      [JFFS2] Reduce visibility of raw_node_ref to upper layers of JFFS2 code. · 2f785402
      David Woodhouse 提交于
      As the first step towards eliminating the ref->next_phys member and saving
      memory by using an _array_ of struct jffs2_raw_node_ref per eraseblock,
      stop the write functions from allocating their own refs; have them just
      _reserve_ the appropriate number instead. Then jffs2_link_node_ref() can
      just fill them in.
      
      Use a linked list of pre-allocated refs in the superblock, for now. Once
      we switch to an array, it'll just be a case of extending that array.
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      2f785402
  9. 22 5月, 2006 2 次提交
  10. 21 5月, 2006 2 次提交
  11. 07 11月, 2005 3 次提交
  12. 06 11月, 2005 1 次提交
  13. 15 7月, 2005 1 次提交
  14. 23 5月, 2005 7 次提交
  15. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4