[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20151008072246.00d423ea@canb.auug.org.au>
Date: Thu, 8 Oct 2015 07:22:46 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Cc: "Nicholas A. Bellinger" <nab@...ux-iscsi.org>,
Greg KH <greg@...ah.com>, Arnd Bergmann <arnd@...db.de>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Christoph Hellwig <hch@....de>
Subject: Re: linux-next: build failure after merge of the target-updates
tree
Hi Alexander,
On Wed, 07 Oct 2015 15:27:17 +0300 Alexander Shishkin <alexander.shishkin@...ux.intel.com> wrote:
>
> Stephen Rothwell <sfr@...b.auug.org.au> writes:
>
> > Caused by commit
> >
> > 7bd1d4093c2f ("stm class: Introduce an abstraction for System Trace Module devices")
> >
> > from the char-misc tree interacting with commit
> >
> > f71933438300 ("configfs: remove old API")
> >
> > I have reverted the target-updated commit for today. If there is a
> > better resolution (and I assume that there is), please let me know.
>
> I'm going to follow up to this email with a fix that updates stm class
> code to the new api, I'm not sure whos branch it should go to, because
> it only works with Christoph's configfs patches in the -next.
Well, I will add it as a merge resolution patch in linux-next (instead
of the current revert) but someone will have to remember to send it to
Linus when the latter of these two trees is merged by him. Unless one
of these trees can merge the other (or a non rebasing subset) ...
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
--
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