public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/2] alpha: fix build failure
Date: Tue, 15 Sep 2015 19:20:49 +0530	[thread overview]
Message-ID: <20150915135048.GA7996@sudip-pc> (raw)
In-Reply-To: <55F81D08.9000808@roeck-us.net>

On Tue, Sep 15, 2015 at 06:28:40AM -0700, Guenter Roeck wrote:
> On 09/15/2015 01:21 AM, Sudip Mukherjee wrote:
> >On Mon, Sep 14, 2015 at 02:22:08PM -0700, Guenter Roeck wrote:
> >>On Mon, Sep 14, 2015 at 05:19:27PM +0530, Sudip Mukherjee wrote:
> 
> I am not building m32r:allmodconfig or openrisc:allmodconfig.
> 
> You can always check http://server.roeck-us.net:8010/builders to see
> what is covered by my builds and tests.
ok, openrisc:defconfig and allnoconfig.

Well, the first error on allmodconfig is:
drivers/vhost/vhost.c: In function 'vhost_vring_ioctl':
drivers/vhost/vhost.c:818:3: error: call to '__compiletime_assert_818' declared with attribute error: BUILD_BUG_ON failed: __alignof__
*vq->avail > VRING_AVAIL_ALIGN_SIZE

Any hint about this one?

regards
sudip

  reply	other threads:[~2015-09-15 13:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 11:49 [PATCH 0/2] alpha: fix build failure Sudip Mukherjee
2015-09-14 11:49 ` [PATCH 1/2] alpha: io: define ioremap_uc Sudip Mukherjee
2015-09-14 11:49 ` [PATCH 2/2] alpha: lib: export __delay Sudip Mukherjee
2015-09-14 21:22 ` [PATCH 0/2] alpha: fix build failure Guenter Roeck
2015-09-14 21:29   ` Andrew Morton
2015-09-14 23:22     ` Guenter Roeck
2015-09-15  8:21   ` Sudip Mukherjee
2015-09-15 13:28     ` Guenter Roeck
2015-09-15 13:50       ` Sudip Mukherjee [this message]
2015-09-15 14:26         ` Guenter Roeck
2015-09-16  5:58           ` Sudip Mukherjee

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=20150915135048.GA7996@sudip-pc \
    --to=sudipm.mukherjee@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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