* Greg KH <greg@xxxxxxxxx>: > On Sat, May 14, 2011 at 10:09:46AM -0700, Yinghai Lu wrote: > > On 05/14/2011 07:35 AM, Greg KH wrote: > > > On Fri, May 13, 2011 at 07:03:48PM -0700, Yinghai Lu wrote: > > ... > > > > >> thought if it is with testing, we can remove it if need to. > > > > > > Unfortunatly, no, everything ends up under "testing". And as there are > > > tools that use this, how are you going to handle angry users that have > > > their systems suddenly broken? > > > > > > > how about only create rescan for pci bridges instead? > > Fine with me. > > Alex? Sorry for delayed response, I've been travelling. My opinion is that Yinghai should write two patches: 1) add 'rescan' for PCI bridges 2) start deprecation process for 'rescan' under devices We can help with the wording on (2). In fact, I think Konrad already improved the text quite a bit. I can contact the users I know about, namely some internal HP software that was written when I was still there. I think the standard deprecation process is appropriate for upstream. thanks, /ac -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
