mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Tair Rzayev <tair.rzayev@gmail.com>
Cc: swetland@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: android: binder.c: Use more appropriate functions for euid retrieval
Date: Sat, 31 May 2014 13:19:11 -0700	[thread overview]
Message-ID: <20140531201911.GB3082@kroah.com> (raw)
In-Reply-To: <20140531201834.GA3082@kroah.com>

On Sat, May 31, 2014 at 01:18:34PM -0700, Greg KH wrote:
> On Sat, May 31, 2014 at 11:03:44PM +0300, Tair Rzayev wrote:
> > 
> > 
> > On 2014.05.31. 22:52, Greg KH wrote:
> > > What kernel tree did you make this against?  It doesn't seem to match up
> > > with what is in my staging-next branch to merge with Linus for the next
> > > release, so please work against that one.
> > 
> > Made against staging-next branch of your linux-next staging tree.
> 
> Hm, it doesn't apply there:
> 
> checking file drivers/staging/android/binder.c
> Reversed (or previously applied) patch detected!  Assume -R? [n]
> Apply anyway? [n]
> Skipping patch.
> 4 out of 4 hunks ignored
> 
> Are you sure you got the right branch?
> 
> > > Oh, and I think this is already been done, although in a bit different
> > > way there, please check to make sure it is correct.
> > 
> > Yes, I have noticed the changes after I have made the patch but I
> > thought mine are a bit cleaner so I have rebased the patch against the
> > changes that are already applied.
> 
> Something went wrong when you made this :(

Oh crap, _I_ was looking at the wrong branch here, nevermind, this
applies just fine.

Sorry for the noise...

greg k-h

      reply	other threads:[~2014-05-31 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31 19:43 Tair Rzayev
2014-05-31 19:52 ` Greg KH
2014-05-31 20:03   ` Tair Rzayev
2014-05-31 20:18     ` Greg KH
2014-05-31 20:19       ` Greg KH [this message]

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=20140531201911.GB3082@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swetland@google.com \
    --cc=tair.rzayev@gmail.com \
    /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

all inboxes | Powered by JetHome®