linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shyam Saini <mayhs11saini@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: labbott@redhat.com, sumit.semwal@linaro.org,
	linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	arve@android.com
Subject: Re: [PATCH 1/1] Staging: android: ion: Remove explicit NULL comparison using Coccinelle
Date: Sun, 02 Oct 2016 21:37:17 +0530	[thread overview]
Message-ID: <1475424437.4301.11.camel@gmail.com> (raw)
In-Reply-To: <20161002153751.GA20900@kroah.com>

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 <mayhs11saini@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

  reply	other threads:[~2016-10-02 16:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28 15:28 [PATCH 1/1] Staging: android: ion: Remove explicit NULL comparison using Coccinelle shyam saini
2016-10-02 14:58 ` Greg KH
2016-10-02 15:21   ` Shyam Saini
2016-10-02 15:37     ` Greg KH
2016-10-02 16:07       ` Shyam Saini [this message]
2016-10-02 16:16         ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1475424437.4301.11.camel@gmail.com \
    --to=mayhs11saini@gmail.com \
    --cc=arve@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sumit.semwal@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).