On Sun, 2016-10-02 at 17:37 +0200, Greg KH wrote: > On Sun, Oct 02, 2016 at 08:51:29PM +0530, Shyam Saini wrote: > > > > On Sun, 2016-10-02 at 16:58 +0200, Greg KH wrote: > > > > > > On Wed, Sep 28, 2016 at 08:58:51PM +0530, shyam saini wrote: > > > > > > > > > > > > Remove the explicit NULL comparison and rewrite in a compact > > > > form. > > > > > > > > Signed-off-by: shyam saini <mayhs11sa...@gmail.com> > > > > --- > > > > drivers/staging/android/ion/ion_of.c | 2 +- > > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > Does not apply to my tree :( > > > > Do I need to rebase it? Because I have already included all the > > maintainers in the patch which I got from > > scripts/get_maintainer.pl. > If you want it applied, yes, you need to rebase it. Listing the > maintainers doesn't help the patch to somehow magically be able to be > applied to the tree :) > > Please work against my staging-testing branch of the staging.git > tree, > as it has a lot of patches I just accepted in it that are not yet in > linux-next. > > thanks, > > greg k-h
>From now onward I will be working on your staging-testing tree. But then why some of my patches which were based on linux-next were accepted? for example today You've accepted my patch "Staging: vt6655: Remove explicit NULL comparison using Coccinelle" with commit id 4d932504b534584e116b400dd6e7b8ce7deb455c, which you can check on git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git This patch was based on linux-next tree. Please clear my confusion. Thanks, Shyam
