From: Vinod Koul <vinod.koul@intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.jf.intel.com>,
Mark Brown <broonie@kernel.org>,
kbuild test robot <fengguang.wu@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.jf.intel.com>,
kbuild-all@01.org, linux-next@vger.kernel.org
Subject: Re: [slave-dma:for-linus 20/20] drivers/spi/spi-pxa2xx-pci.c:70:3: error: unknown field 'max_clk_rate' specified in initializer
Date: Tue, 16 Sep 2014 13:49:39 +0530 [thread overview]
Message-ID: <20140916081939.GN3131@intel.com> (raw)
In-Reply-To: <1410852955.7023.50.camel@linux.intel.com>
On Tue, Sep 16, 2014 at 10:35:55AM +0300, Andy Shevchenko wrote:
> On Tue, 2014-09-16 at 10:22 +0530, Vinod Koul wrote:
> > On Mon, Sep 15, 2014 at 11:06:40AM +0300, Mika Westerberg wrote:
> > > On Sat, Sep 13, 2014 at 10:00:53AM -0700, Mark Brown wrote:
> > > > On Thu, Sep 11, 2014 at 01:17:50PM +0300, Mika Westerberg wrote:
> > > >
> > > > > Vinod, this has dependency to the SPI tree. I suppose right way to
> > > > > handle this is to merge Mark's topic/pxa2xx branch into this. Or
> > > > > alternatively Mark can make an immutable branch containing the missing
> > > > > commit that you can merge.
> > > >
> > > > I've tagged this here, please do remember to coordinate dependencies
> > > > when making this sort of multi-tree change:
> > >
> > > Thanks Mark!
> > >
> > > Vinod, can you pull this to your -next branch?
> > Done, can you verify merge was okay as I had few conflicts.
>
> There is one line missed:
>
> + .max_clk_rate = 50000000,
>
> In the PORT_BYT section of the spi_info_configs[].
Okay fixed this one..
--
~Vinod
prev parent reply other threads:[~2014-09-16 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5411735d.SAoL/AZyi+bJWC6n%fengguang.wu@intel.com>
[not found] ` <20140911101750.GP13406@lahna.fi.intel.com>
2014-09-13 17:00 ` [slave-dma:for-linus 20/20] drivers/spi/spi-pxa2xx-pci.c:70:3: error: unknown field 'max_clk_rate' specified in initializer Mark Brown
2014-09-15 8:06 ` Mika Westerberg
2014-09-16 4:52 ` Vinod Koul
2014-09-16 7:35 ` Andy Shevchenko
2014-09-16 8:19 ` Vinod Koul [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=20140916081939.GN3131@intel.com \
--to=vinod.koul@intel.com \
--cc=andriy.shevchenko@linux.jf.intel.com \
--cc=broonie@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-next@vger.kernel.org \
--cc=mika.westerberg@linux.jf.intel.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.