On Sun, Mar 30, 2014 at 06:04:33PM -0400, Tejun Heo wrote:
> On Sun, Mar 30, 2014 at 09:26:41AM -0700, Greg Kroah-Hartman wrote:
> > On Sun, Mar 30, 2014 at 09:13:09AM -0400, Tejun Heo wrote:
> > > Oops, this is not for driver-core-next but driver-core-linus.
> >
> > It's _really_ late in the rele
On Sun, Mar 30, 2014 at 09:26:41AM -0700, Greg Kroah-Hartman wrote:
> On Sun, Mar 30, 2014 at 09:13:09AM -0400, Tejun Heo wrote:
> > Oops, this is not for driver-core-next but driver-core-linus.
>
> It's _really_ late in the release cycle for something like this, can I
> add it to 3.15-rc1 and if
On Sun, Mar 30, 2014 at 09:13:09AM -0400, Tejun Heo wrote:
> Oops, this is not for driver-core-next but driver-core-linus.
It's _really_ late in the release cycle for something like this, can I
add it to 3.15-rc1 and if people are seeing issues, backport it to
3.14-stable?
thanks,
greg k-h
--
To
Oops, this is not for driver-core-next but driver-core-linus.
Thanks!
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ a
Long ago, sysfs used to depend on vfs data structures for internal
representation and thus needed to make a hidden mount to make them
available. sysfs stopped depending on vfs for internal representation
long ago and 9e30cc959530 ("sysfs, kernfs: no need to kern_mount()
sysfs from sysfs_init()") r
5 matches
Mail list logo