All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Marian Chereji <marian.chereji@freescale.com>,
	Catalina Mocanu <catalina.mocanu@gmail.com>
Subject: Re: linux-next: manual merge of the akpm-current tree with the tiny tree
Date: Mon, 10 Nov 2014 09:58:57 -0800	[thread overview]
Message-ID: <20141110175856.GD18766@thin> (raw)
In-Reply-To: <20141110195912.324b90ed@canb.auug.org.au>

On Mon, Nov 10, 2014 at 07:59:12PM +1100, Stephen Rothwell wrote:
> Hi Andrew,
> 
> Today's linux-next merge of the akpm-current tree got a conflict in
> lib/Kconfig between commit 3a8aeefbd4e9 ("lib: halfmd4: Make halfmd4.c
> optional") from the tiny tree and commit c7f379b518a3 ("lib: Add CRC64
> ECMA module") from the akpm-current tree.
> 
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).

Looks good.

- Josh Triplett

> diff --cc lib/Kconfig
> index b8c97f05140d,2faf7b2de5b3..000000000000
> --- a/lib/Kconfig
> +++ b/lib/Kconfig
> @@@ -186,9 -180,13 +186,16 @@@ config CRC
>   	  when they need to do cyclic redundancy check according CRC8
>   	  algorithm. Module will be called crc8.
>   
> + config CRC64_ECMA
> + 	tristate "CRC64 ECMA function"
> + 	help
> + 	  This option provides CRC64 ECMA function. Drivers may select this
> + 	  when they need to do cyclic redundancy check according to the CRC64
> + 	  ECMA algorithm.
> + 
>  +config HALFMD4
>  +	bool
>  +
>   config AUDIT_GENERIC
>   	bool
>   	depends on AUDIT && !AUDIT_ARCH

      reply	other threads:[~2014-11-10 17:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10  8:59 linux-next: manual merge of the akpm-current tree with the tiny tree Stephen Rothwell
2014-11-10 17:58 ` Josh Triplett [this message]

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=20141110175856.GD18766@thin \
    --to=josh@joshtriplett.org \
    --cc=akpm@linux-foundation.org \
    --cc=catalina.mocanu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=marian.chereji@freescale.com \
    --cc=sfr@canb.auug.org.au \
    /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.