public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michael Zoran <mzoran@crowfest.net>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	devel@driverdev.osuosl.org, Daniel Stone <daniels@collabora.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Lee Jones <lee@kernel.org>,
	linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>,
	linux-rpi-kernel@lists.infradead.org,
	popcornmix <popcornmix@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] staging/vc04_services: initialize cache line size properly
Date: Mon, 6 Mar 2017 13:53:34 +0100	[thread overview]
Message-ID: <20170306125334.GC26115@kroah.com> (raw)
In-Reply-To: <1488419978.20502.1.camel@crowfest.net>

On Wed, Mar 01, 2017 at 05:59:38PM -0800, Michael Zoran wrote:
> Hi Arnd,
> 
> I submitted a change which is in Linux-next now that makes the whole
> CACHE_LINE_SIZE macro meaningless.  It now always reads the size from
> the DT and errors out with -ENODEV if the property is missing.
> 
> I was going to submit a change to delete the macro completely, just
> never got to it.
> 
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit
> /drivers/staging/vc04_services/interface?id=6cf1bf636a067eb308cb3a8322b
> 9d6b1844a075d

This should be in 4.11-rc1.

thanks,

greg k-h

      reply	other threads:[~2017-03-06 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 22:50 [PATCH 1/2] staging/vc04_services: initialize cache line size properly Arnd Bergmann
2017-03-01 22:50 ` [PATCH 2/2] staging/vc04_services: add CONFIG_OF dependency Arnd Bergmann
2017-03-02  1:59 ` [PATCH 1/2] staging/vc04_services: initialize cache line size properly Michael Zoran
2017-03-06 12:53   ` Greg Kroah-Hartman [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=20170306125334.GC26115@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=daniels@collabora.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=eric@anholt.net \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=mzoran@crowfest.net \
    --cc=popcornmix@gmail.com \
    --cc=stefan.wahren@i2se.com \
    --cc=swarren@wwwdotorg.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