On Thu, Dec 06, 2018 at 08:37:41AM -0800, Todd Kjos wrote: > On Thu, Dec 6, 2018 at 6:51 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > On Wed, Dec 05, 2018 at 03:19:24PM -0800, Todd Kjos wrote: > > > Add __acquire()/__release() annnotations to fix warnings > > > in sparse context checking > > > > > > There is one case where the warning was due to a lack of > > > a "default:" case in a switch statement where a lock was > > > being released in each of the cases, so the default > > > case was added. > > > > > > Signed-off-by: Todd Kjos <tkjos@xxxxxxxxxx> > > > --- > > > v2: no change, just resubmitted as #1 of 3 patches instead of by itself > > > > I've already applied this one, right? > > No, not yet. I confused you by failing to add the "v2" in the subject > for the other two submitted with it that you applied this morning: > > binder: filter out nodes when showing binder procs > binder: fix kerneldoc header for struct binder_buffer > > Sorry about the confusion. This one still needs to be applied. But I thought I applied this back on November 26: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/commit/?h=char-misc-testing&id=324fa64cf4189094bc4df744a9e7214a1b81d845 You should have gotten an email from my scripts at that time. or is this somehow a different patch with the same commit log? Or a v2 that changed from the one that I had applied? Do I need to revert this one and apply your new one? confused, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
