On Fri, Jan 11, 2019 at 10:18:18AM +0100, Greg KH wrote: > On Wed, Jan 02, 2019 at 12:32:19PM +0100, Christian Brauner wrote: > > The binderfs instance in the initial ipc namespace will always have a > > reserve of 4 binder devices unless explicitly capped by specifying a lower > > value via the "max" mount option. > > This ensures when binder devices are removed (on accident or on purpose) > > they can always be recreated without risking that all minor numbers have > > already been used up. > > > > Cc: Todd Kjos <tkjos@xxxxxxxxxx> > > Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > > Signed-off-by: Christian Brauner <christian.brauner@xxxxxxxxxx> > > --- > > v2: > > - patch unchanged > > v1: > > - patch introduced > > v0: > > - patch not present > > --- > > drivers/android/binderfs.c | 7 ++++++- > > 1 file changed, 6 insertions(+), 1 deletion(-) > > What did you make this patch against? It doesn't apply cleanly so I > don't want to take it until we get everything synced up properly > together :( > > I'll apply patch 1/2 now, can you rebase and resend this one? Yup. I'll rebase on top of char-misc-linus now. :) Thanks! Christian _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
