All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <dborkman@redhat.com>
To: Markos Chandras <Markos.Chandras@imgtec.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux MIPS Mailing List <linux-mips@linux-mips.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	Alexei Starovoitov <ast@plumgrid.com>
Subject: Re: mips:allmodconfig build failure in 3.16-rc1 due to bpf_jit code
Date: Tue, 17 Jun 2014 13:21:09 +0200	[thread overview]
Message-ID: <53A024A5.9040108@redhat.com> (raw)
In-Reply-To: <53A021E8.8020209@imgtec.com>

On 06/17/2014 01:09 PM, Markos Chandras wrote:
...
> Thanks for these instructions. I will try them myself once I find some
> time since I don't think bpf_jit for MIPS has ever been tested with all
> the opcodes.

Sounds great! If you find some tests are missing, please feel free to
submit them as well via netdev.

Best,

Daniel

  reply	other threads:[~2014-06-17 13:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17  2:24 mips:allmodconfig build failure in 3.16-rc1 due to bpf_jit code Guenter Roeck
2014-06-17  8:20 ` Daniel Borkmann
2014-06-17 10:16   ` Daniel Borkmann
2014-06-17 10:16     ` Daniel Borkmann
2014-06-17 10:39     ` Guenter Roeck
2014-06-17 10:56       ` Daniel Borkmann
2014-06-17 11:09         ` Markos Chandras
2014-06-17 11:21           ` Daniel Borkmann [this message]
2014-06-17 10:54     ` Markos Chandras
2014-06-17 10:58       ` Daniel Borkmann
  -- strict thread matches above, loose matches on Subject: below --
2014-06-17 19:38 Alexei Starovoitov
2014-06-18  8:28 ` Markos Chandras

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=53A024A5.9040108@redhat.com \
    --to=dborkman@redhat.com \
    --cc=Markos.Chandras@imgtec.com \
    --cc=ast@plumgrid.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux@roeck-us.net \
    --cc=ralf@linux-mips.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.