All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolai Stange <nicstange@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Nicolai Stange <nicstange@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	daniel@iogearbox.net
Subject: Re: [PATCH] lib: test_bpf: purge CPP register redefinitions
Date: Mon, 22 Jun 2015 15:47:12 +0200	[thread overview]
Message-ID: <87egl3lusf.fsf@gmail.com> (raw)
In-Reply-To: <5587B4FB.3040609@nod.at> (Richard Weinberger's message of "Mon, 22 Jun 2015 09:10:51 +0200")

Richard Weinberger <richard@nod.at> writes:
> While riding the bus to my office I've materialized that idea.
> Nicolai, can you please give the attached patch a try?
W/o my test_bpf patch applied, w/ your patch applied:
 - linux mainline: um compiles
 - linux-next: um compiles up to this mfd/syscon issue communicated to
               you in sidechannel

In particular, your patch fixes, next to [0], the issue addressed by my
patch.

-> My 1K line regexp replace patch reduces to a debatable naming style
   patch. Drop it, sorry for the noise.

[0] http://lkml.kernel.org/r/1420386535-22530-1-git-send-email-richard@nod.at
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/

WARNING: multiple messages have this Message-ID (diff)
From: Nicolai Stange <nicstange@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Nicolai Stange <nicstange@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	daniel@iogearbox.net
Subject: Re: [PATCH] lib: test_bpf: purge CPP register redefinitions
Date: Mon, 22 Jun 2015 15:47:12 +0200	[thread overview]
Message-ID: <87egl3lusf.fsf@gmail.com> (raw)
In-Reply-To: <5587B4FB.3040609@nod.at> (Richard Weinberger's message of "Mon, 22 Jun 2015 09:10:51 +0200")

Richard Weinberger <richard@nod.at> writes:
> While riding the bus to my office I've materialized that idea.
> Nicolai, can you please give the attached patch a try?
W/o my test_bpf patch applied, w/ your patch applied:
 - linux mainline: um compiles
 - linux-next: um compiles up to this mfd/syscon issue communicated to
               you in sidechannel

In particular, your patch fixes, next to [0], the issue addressed by my
patch.

-> My 1K line regexp replace patch reduces to a debatable naming style
   patch. Drop it, sorry for the noise.

[0] http://lkml.kernel.org/r/1420386535-22530-1-git-send-email-richard@nod.at

  reply	other threads:[~2015-06-22 13:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21 19:41 [PATCH] lib: test_bpf: purge CPP register redefinitions Nicolai Stange
2015-06-21 19:41 ` Nicolai Stange
2015-06-22  6:05 ` Alexei Starovoitov
2015-06-22  6:05   ` Alexei Starovoitov
2015-06-22  6:52   ` Richard Weinberger
2015-06-22  6:52     ` Richard Weinberger
2015-06-22  7:10     ` Richard Weinberger
2015-06-22 13:47       ` Nicolai Stange [this message]
2015-06-22 13:47         ` Nicolai Stange
2015-06-23 13:47         ` David Miller
2015-06-23 13:47 ` David Miller

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=87egl3lusf.fsf@gmail.com \
    --to=nicstange@gmail.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richard@nod.at \
    /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.