linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Dec 12
Date: Fri, 12 Dec 2014 10:49:17 +0100	[thread overview]
Message-ID: <1418377757.5756.24.camel@x220> (raw)
In-Reply-To: <20141212183518.06e3803d@canb.auug.org.au>

Hi Stephen,

On Fri, 2014-12-12 at 18:35 +1100, Stephen Rothwell wrote:
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au

(Side note: it took me some time to realize that evolution automagically
removes the above lines and the log that follows because it is
considered one humongous signature. Maybe there's a setting to stop
evolution doing that. Anyhow, I copied the quotes in this message by
hand.)

> $ git checkout master
> $ git reset --hard stable
> [...]
> Merging akpm-current/current (35ac317b788c shmdt: use i_size_read() instead of ->i_size)
> CONFLICT (content): Merge conflict in tools/testing/selftests/Makefile
> CONFLICT (content): Merge conflict in mm/page_alloc.c
> CONFLICT (content): Merge conflict in mm/memcontrol.c
> CONFLICT (content): Merge conflict in mm/hugetlb.c
> CONFLICT (content): Merge conflict in kernel/printk/printk.c
> CONFLICT (content): Merge conflict in kernel/exit.c
> CONFLICT (content): Merge conflict in init/main.c

I think the conflict resolution here can be found in your merge commit
bcab756e1d32 ("Merge branch 'akpm-current/current'").

For some reason it removes the only check for CONFIG_INIT_FALLBACK. I
only noticed because that makes the Kconfig entry INIT_FALLBACK a nop.
That check and Kconfig entry were added in commit 6ef4536e2f19 ("init:
allow CONFIG_INIT_FALLBACK=n to disable defaults if init= fails"). That
commit debuted in today's linux-next.

Anyhow, I'm sure this all will be sorted out in due time.

> CONFLICT (content): Merge conflict in include/linux/mmzone.h
> CONFLICT (content): Merge conflict in fs/proc/task_mmu.c
> CONFLICT (content): Merge conflict in fs/ocfs2/inode.h
> CONFLICT (content): Merge conflict in fs/binfmt_misc.c
> CONFLICT (content): Merge conflict in drivers/usb/storage/debug.c
> CONFLICT (content): Merge conflict in drivers/rtc/rtc-omap.c
> CONFLICT (content): Merge conflict in drivers/rtc/rtc-isl12057.c
> CONFLICT (content): Merge conflict in drivers/rtc/rtc-ds1374.c
> CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/vendor-prefixes.txt
> CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/i2c/trivial-devices.txt

Thanks,


Paul Bolle

  reply	other threads:[~2014-12-12  9:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12  7:35 linux-next: Tree for Dec 12 Stephen Rothwell
2014-12-12  9:49 ` Paul Bolle [this message]
2014-12-12 10:04   ` Stephen Rothwell
2014-12-12 10:31     ` Paul Bolle
2014-12-12 21:57       ` Andrew Morton
2014-12-12 22:36         ` Paul Bolle
2014-12-12 22:56           ` Andrew Morton
2014-12-13  4:10             ` Stephen Rothwell
2014-12-12 19:00 ` linux-next: Tree for Dec 12 (sound/soc/codecs/rt5640) Randy Dunlap
2014-12-12 21:15 ` linux-next: Tree for Dec 12 (net/bridge) Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2023-12-12  3:32 linux-next: Tree for Dec 12 Stephen Rothwell
2023-12-12  6:25 ` Stephen Rothwell
2019-12-12  4:50 Stephen Rothwell
2018-12-12  6:32 Stephen Rothwell
2017-12-12  5:29 Stephen Rothwell
2016-12-12  6:39 Stephen Rothwell
2013-12-12  6:06 Stephen Rothwell
2011-12-12  5:14 Stephen Rothwell
2011-12-12 21:26 ` Konrad Rzeszutek Wilk

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=1418377757.5756.24.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=valentinrothberg@gmail.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;
as well as URLs for NNTP newsgroup(s).