public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: Rob Clark <robdclark@gmail.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Maarten Lankhorst <maarten.lankhorst@canonical.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fence: Use smp_mb__before_atomic()
Date: Thu, 5 Jun 2014 08:51:03 -0700	[thread overview]
Message-ID: <20140605155103.GB23993@kroah.com> (raw)
In-Reply-To: <CAO_48GG0Gm3d7=CkT+z00-f7RSy7snAg4Vkes1c5J6ZXXELWPQ@mail.gmail.com>

On Thu, Jun 05, 2014 at 05:56:36PM +0530, Sumit Semwal wrote:
> Hi Greg,
> Pending agreement on the need of fence.c (Rob has given the most
> prominent use case for it, and the lack of existing mechanisms to use
> already),

See my disagreement there :)

> would you be ok if I move all the dma-buf* and related (fence.c etc)
> to its own subdirectory and queue it up for this release?

This release (i.e. 3.16) is way too early.  You need to get agreement of
what gets into linux-next first, tested there, and then you can get it
merged into Linus's tree.

In the middle of the merge window is not the time to be moving files
around and disagreeing on if the code is needed or not at all.

So, again, please drop the code from your trees (or whomever trees this
code is in), resend it, notifying everyone involved, and we can take it
from there.

And yes, to be clear, this isn't going to make 3.16, sorry.

thanks,

gre k-h

  reply	other threads:[~2014-06-05 15:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28 14:26 [PATCH] fence: Use smp_mb__before_atomic() Thierry Reding
2014-05-28 20:16 ` Maarten Lankhorst
2014-05-28 20:51 ` Greg Kroah-Hartman
2014-05-30  8:15   ` Thierry Reding
2014-05-30 16:08     ` Greg Kroah-Hartman
2014-06-04 11:27       ` Sumit Semwal
2014-06-04 13:28         ` Thierry Reding
2014-06-04 17:49           ` Greg Kroah-Hartman
2014-06-05 11:51             ` Rob Clark
2014-06-05 12:00               ` Maarten Lankhorst
2014-06-05 15:52                 ` Greg Kroah-Hartman
2014-06-05 12:26               ` Sumit Semwal
2014-06-05 15:51                 ` Greg Kroah-Hartman [this message]
2014-06-05 15:48               ` Greg Kroah-Hartman
2014-06-05 16:39                 ` Sumit Semwal
2014-06-05 17:49                   ` Greg Kroah-Hartman
2014-06-05 21:56                 ` Rob Clark
2014-06-04 17:48         ` Greg Kroah-Hartman

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=20140605155103.GB23993@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@canonical.com \
    --cc=robdclark@gmail.com \
    --cc=sumit.semwal@linaro.org \
    --cc=thierry.reding@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