public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>, Greg KH <greg@kroah•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Masanari Iida <standby24x7@gmail•com>,
	Mel Gorman <mgorman@techsingularity•net>
Subject: linux-next: manual merge of the akpm-current tree with the usb tree
Date: Wed, 7 Oct 2015 15:26:08 +1100	[thread overview]
Message-ID: <20151007152608.2ba8f7a5@canb.auug.org.au> (raw)

Hi Andrew,

Today's linux-next merge of the akpm-current tree got a conflict in:

  drivers/usb/host/u132-hcd.c

between commit:

  d5f9e73309b7 ("USB: u132-hcd: Fix seperate word in printk message")

from the usb tree and commit:

  ac4f832eb227 ("mm, page_alloc: distinguish between being unable to sleep, unwilling to sleep and avoiding waking kswapd")

from the akpm-current tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

diff --cc drivers/usb/host/u132-hcd.c
index 0a94895a358d,67b3b9d9dfd1..000000000000
--- a/drivers/usb/host/u132-hcd.c
+++ b/drivers/usb/host/u132-hcd.c
@@@ -2244,8 -2244,9 +2244,8 @@@ static int u132_urb_enqueue(struct usb_
  {
  	struct u132 *u132 = hcd_to_u132(hcd);
  	if (irqs_disabled()) {
- 		if (__GFP_WAIT & mem_flags) {
+ 		if (gfpflags_allow_blocking(mem_flags)) {
 -			printk(KERN_ERR "invalid context for function that migh"
 -				"t sleep\n");
 +			printk(KERN_ERR "invalid context for function that might sleep\n");
  			return -EINVAL;
  		}
  	}

                 reply	other threads:[~2015-10-07  4:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20151007152608.2ba8f7a5@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=greg@kroah$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mgorman@techsingularity$(echo .)net \
    --cc=standby24x7@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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