> > The plaintiff makes a valid point. How about a staging approach: We
put
> > the patch as it is now into 2.6.23 so the problem is fixed, and I'll
post
> > a "nice" version with autoloading support and a generic of_make_bus_id
> > function for 2.6.24. Agree?
>
> Ok, sounds fair. Can you make sure that the resulting bus_id is the same
> for the final version then?
No, it would change once more -- the current, minimal-invasive, variant of
the fix uses the full_name -> "ehca@12345678", while of_make_bus_id uses
another format: "12345678.ehca". I don't think this makes much of a
difference, though, and users shouldn't rely on the bus_id having a
certain format anyway, so IMHO we can live with this.
Regards,
Joachim
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
