From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Maarten Lankhorst <maarten.lankhorst@canonical.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fence: Use smp_mb__before_atomic()
Date: Fri, 30 May 2014 09:08:31 -0700 [thread overview]
Message-ID: <20140530160831.GA11182@kroah.com> (raw)
In-Reply-To: <20140530081504.GA16669@ulmo>
On Fri, May 30, 2014 at 10:15:05AM +0200, Thierry Reding wrote:
> On Wed, May 28, 2014 at 01:51:45PM -0700, Greg Kroah-Hartman wrote:
> > On Wed, May 28, 2014 at 04:26:32PM +0200, Thierry Reding wrote:
> > > From: Thierry Reding <treding@nvidia.com>
> > >
> > > Commit febdbfe8a91c (arch: Prepare for smp_mb__{before,after}_atomic())
> > > deprecated the smp_mb__{before,after}_{atomic,clear}_{dec,inc,bit}*()
> > > functions in favour of the unified smp_mb__{before,after}_atomic().
> > >
> > > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > > ---
> > > drivers/base/fence.c | 4 ++--
> >
> > Where does this file come from? I've not seen it before, and it's not
> > in my tree.
>
> I think it came in through Sumit's tree and it's only in linux-next I
> believe.
Odd, linux-next is for merging things in Linus's next release.
And as I have never seen this code that will end up being my
responsibility to maintain, it seems strange that it will be merged in
the next kernel development cycle.
What broke down here with our review process that required something to
be merged without at least a cc: to me?
greg k-h
next prev parent reply other threads:[~2014-05-30 16:04 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 [this message]
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
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=20140530160831.GA11182@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.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