All of lore.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Roland Dreier <roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: linux-next: build failure after merge of the infiniband tree
Date: Thu, 16 Aug 2012 09:24:27 +0300	[thread overview]
Message-ID: <502C921B.7000202@mellanox.com> (raw)
In-Reply-To: <CAG4TOxNLenjQxZNb7Rpm2G9RNBN77uWgEgfNXgoj+gLFdObuTg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 16/08/2012 07:07, Roland Dreier wrote:
> [...] should be fixed in tomorrow's for-next (added include of 
> <linux/vmalloc.h>). 

thanks for taking care of that.
>> See Rule 1 in Documentation/SubmitChecklist.
>
> Heh, but it compiles fine on x86!

I wonder if there is a way to easily catch such errors when building on x86.

Or.



--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-08-16  6:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  1:44 linux-next: build failure after merge of the infiniband tree Stephen Rothwell
2012-08-16  4:07 ` Roland Dreier
     [not found]   ` <CAG4TOxNLenjQxZNb7Rpm2G9RNBN77uWgEgfNXgoj+gLFdObuTg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-16  6:24     ` Or Gerlitz [this message]
2012-08-16  6:59     ` Stephen Rothwell
2012-08-16  6:59       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2015-02-18  2:32 Stephen Rothwell
2015-02-18  3:01 ` Roland Dreier
2014-12-16  1:47 Stephen Rothwell
2014-12-16  1:47 ` Stephen Rothwell
     [not found] ` <20141216124750.153e3fdd-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2014-12-16  1:56   ` Roland Dreier
2014-12-16  1:56     ` Roland Dreier
2014-12-16  2:22     ` Roland Dreier
     [not found]     ` <CAG4TOxP9WFHALPb0y0eKFup6uhszXfd+hLcwZ98kZUVaR_9j4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-16 10:57       ` Or Gerlitz
2014-12-16 10:57         ` Or Gerlitz
2012-12-19 22:44 Stephen Rothwell
2012-12-19 22:44 ` Stephen Rothwell
     [not found] ` <20121220094433.791d70e55ae5e3325a6190fc-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2012-12-20  0:22   ` Roland Dreier
2012-12-20  0:22     ` Roland Dreier
2012-12-20  9:58     ` Vipul Pandya
2012-07-06  2:35 Stephen Rothwell
     [not found] ` <20120706123555.949d8efb4de5c4df18fb1ec0-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2012-07-06  3:58   ` Roland Dreier
2012-07-06  3:58     ` Roland Dreier
2012-07-06  6:31     ` Hefty, Sean
2012-05-21  2:05 Stephen Rothwell
2012-05-21 14:04 ` Vipul Pandya
2012-05-21 16:03   ` Roland Dreier
2011-10-11  3:49 Stephen Rothwell
2010-07-09  1:04 Stephen Rothwell
2010-07-09  3:05 ` Ben Hutchings
     [not found] ` <20100709110427.c05987cc.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-07-09  3:46   ` Roland Dreier
2010-07-09  3:46     ` Roland Dreier
2010-07-09  6:16     ` Stephen Rothwell

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=502C921B.7000202@mellanox.com \
    --to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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 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.