Announcement

Collapse
No announcement yet.

The Staging Pull For Linux 3.20 Has A Lot Of Changes All Over The Place

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • The Staging Pull For Linux 3.20 Has A Lot Of Changes All Over The Place

    Phoronix: The Staging Pull For Linux 3.20 Has A Lot Of Changes All Over The Place

    The latest pull requests sent in for the Linux 3.20 kernel are the various subsystems maintained by Greg Kroah-Hartman. The changes for the USB drivers, char/misc, driver core, staging, and TTY/serial aren't too jaw-dropping, but for staging at least is the usual heavy churn between kernel cycles...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Staging is for experimental stuff isn't it?

    So why is an obsolete driver being pushed to staging instead of being marked as (DEPRECATED) or (OBSOLETE) in the sources?

    Comment


    • #3
      Originally posted by Sonadow View Post
      Staging is for experimental stuff isn't it?

      So why is an obsolete driver being pushed to staging instead of being marked as (DEPRECATED) or (OBSOLETE) in the sources?
      so true

      Comment


      • #4
        Originally posted by Sonadow View Post
        Staging is for experimental stuff isn't it?

        So why is an obsolete driver being pushed to staging instead of being marked as (DEPRECATED) or (OBSOLETE) in the sources?
        Code size is my guess. Though in that case there should be like a deprecated-sources branch or something like that. If something like that happened, there could be a lot of the existing kernel sources that could fit into it.

        Comment


        • #5
          Staging is for experimental stuff isn't it?

          So why is an obsolete driver being pushed to staging instead of being marked as (DEPRECATED) or (OBSOLETE) in the sources?
          Originally posted by duby229 View Post
          Code size is my guess. Though in that case there should be like a deprecated-sources branch or something like that. If something like that happened, there could be a lot of the existing kernel sources that could fit into it.
          Wouldn't this mean they are testing if the removal of this code affects any other system? So it would make sense to add to the staging branch to test it out.

          As with many things, I think Michael just worded it awkwardly. (Which is fine unless it causes confusion.)

          Comment

          Working...
          X