[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <521E3259.6040201@samsung.com>
Date: Wed, 28 Aug 2013 20:24:41 +0300
From: Dmitry Kasatkin <d.kasatkin@...sung.com>
To: Sarah Sharp <sarah.a.sharp@...ux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
sedat.dilek@...il.com, Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>, linux-usb@...r.kernel.org
Subject: Re: linux-next: Tree for Aug 28 [ xhci build breakage ]
On 28/08/13 19:59, Sarah Sharp wrote:
> Please trim your replies.
>
> On Wed, Aug 28, 2013 at 01:53:49PM +0300, Dmitry Kasatkin wrote:
>>>>> That change seems to cause the problems:
>>>>>
>>>>> commit 0730d52a86919300a39a2be37f6c140997dfb82f
>>>>> "xhci:prevent "callbacks suppressed" when debug is not enabled"
>>>>>
>>>>> - Sedat -
>>>>>
>>>>> [1] http://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/drivers/usb/host/xhci-ring.c?h=usb-next&id=0730d52a86919300a39a2be37f6c140997dfb82f
>>>>>
>>>> Hello,
>>>>
>>>> [PATCHv2 1/2] was not applied before.
>>>> I pointed this out few hours ago...
> So commit 0730d52a86919300a39a2be37f6c140997dfb82f 'xhci:prevent
> "callbacks suppressed" when debug is not enabled' needed to be applied
> after your first patch? And basically applying that patch alone breaks
> the build?
Right...
May be I had to stress it somehow... sorry.
> Ugh. Sorry about this. Greg, how do you want to handle this?
>
> Sarah "needs a vacation" Sharp
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists