From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Tero Kristo <t-kristo@ti.com>,
linux-omap mailing list <linux-omap@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: linux-next problems
Date: Thu, 12 Jan 2012 18:05:18 +0200 [thread overview]
Message-ID: <1326384318.1896.20.camel@deskari> (raw)
In-Reply-To: <CAK=WgbbJsfdcjv86y6PC2w1jxCyApL-LFj8PvoKSQDL2e7m4iA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
On Thu, 2012-01-12 at 17:58 +0200, Ohad Ben-Cohen wrote:
> + Stephen
>
> Thanks, Tomi.
>
> On Thu, Jan 12, 2012 at 5:38 PM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> > I was trying to compile linux-next for OMAP, but it doesn't compile with
> > the default configs.
> ...
> > drivers/remoteproc/remoteproc_rpmsg.c:100:6: error: too few arguments to function 'vring_new_virtqueue'
>
> This is due to a recent change in virtio.
>
> Stephen, I guess this won't be relevant for more than a few days, but
> can you please take this patch below to linux-next ?
> (alternatively feel free just to squash this to the merge commit.
> whatever is easiest for you.)
Why don't you just update your for-next branch, and it will be included
into linux-next automatically?
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-12 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 15:38 linux-next problems Tomi Valkeinen
2012-01-12 15:58 ` Ohad Ben-Cohen
2012-01-12 16:05 ` Tomi Valkeinen [this message]
2012-01-12 16:11 ` Ohad Ben-Cohen
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=1326384318.1896.20.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=sfr@canb.auug.org.au \
--cc=t-kristo@ti.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