mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: linux-next: manual merge of the crypto tree with the kbuild tree
Date: Tue, 11 Apr 2017 15:19:51 +0800	[thread overview]
Message-ID: <20170411071951.GA11474@gondor.apana.org.au> (raw)
In-Reply-To: <CAK7LNASesrB5bEvFGxO_BbnqA-h0+TCxMQsmtbv3zqS7gNMe1Q@mail.gmail.com>

On Tue, Apr 11, 2017 at 04:00:45PM +0900, Masahiro Yamada wrote:
>
> Commit 4473710df1f8 fixed the problem,
> but reverting the patch in kbuild will break the bisect'ability
> of the kbuild tree.

All you will be doing is reverting to the status quo before you
applied that patch.  So I don't see how this can break anything
that wasn't already broken.

Cheers,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2017-04-11  7:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11  0:21 Stephen Rothwell
2017-04-11  2:42 ` Herbert Xu
2017-04-11  5:02   ` Stephen Rothwell
2017-04-11  5:12     ` Herbert Xu
2017-04-11  6:34       ` Masahiro Yamada
2017-04-11  6:40         ` Herbert Xu
2017-04-11  7:00           ` Masahiro Yamada
2017-04-11  7:19             ` Herbert Xu [this message]
2017-04-11  7:51     ` Masahiro Yamada
2017-04-11  9:22       ` Herbert Xu

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=20170411071951.GA11474@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=sfr@canb.auug.org.au \
    --cc=yamada.masahiro@socionext.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

all inboxes | Powered by JetHome®