All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Serban Constantinescu <serban.constantinescu@arm.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
	arve@android.com, john.stultz@linaro.org, Dave.Butcher@arm.com
Subject: Re: [PATCH] staging: android: ashmem: add 32bit compat support
Date: Mon, 25 Feb 2013 10:57:35 -0800	[thread overview]
Message-ID: <20130225185735.GA10342@kroah.com> (raw)
In-Reply-To: <1361817876-24747-1-git-send-email-serban.constantinescu@arm.com>

On Mon, Feb 25, 2013 at 06:44:35PM +0000, Serban Constantinescu wrote:
> Hi all,
> 
> As disussed with the Android kernel team I am resubmitting this patch
> without any modifications to the structure exchanged between kernel and
> userspace.

I'll need some acks or signed-off-by: on the patch from them, before I
can take this patch, thanks.

Oh, it's also too late for 3.9, 3.10 is the soonest this can go in, just
to set your expectations properly.

thanks,

greg k-h

      parent reply	other threads:[~2013-02-25 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <staging: android: ashmem: add 32bit compat support>
2013-02-25 18:44 ` [PATCH] staging: android: ashmem: add 32bit compat support Serban Constantinescu
2013-02-25 18:44   ` [PATCH] staging: android: ashmem: Add support for 32bit ashmem calls in a 64bit kernel Serban Constantinescu
2013-02-25 18:55     ` John Stultz
2013-02-25 22:53     ` Arve Hjønnevåg
2013-03-05  8:37     ` Greg KH
2013-03-05 10:18       ` Serban Constantinescu
2013-03-05 10:27         ` Greg KH
2013-03-05 10:38           ` Serban Constantinescu
2013-03-05 10:47             ` Greg KH
2013-03-05 10:25       ` Serban Constantinescu
2013-02-25 18:57   ` 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=20130225185735.GA10342@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Dave.Butcher@arm.com \
    --cc=arve@android.com \
    --cc=john.stultz@linaro.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serban.constantinescu@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.