From: Alexander Shishkin <alexander.shishkin@linux•intel.com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
"Nicholas A. Bellinger" <nab@linux-iscsi•org>,
Greg KH <greg@kroah•com>, Arnd Bergmann <arnd@arndb•de>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Christoph Hellwig <hch@lst•de>
Subject: Re: linux-next: build failure after merge of the target-updates tree
Date: Wed, 07 Oct 2015 15:27:17 +0300 [thread overview]
Message-ID: <87bncaj23e.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20151007144932.3e68e0f7@canb.auug.org.au>
Stephen Rothwell <sfr@canb•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.
Regards,
--
Alex
next prev parent reply other threads:[~2015-10-07 12:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 3:49 linux-next: build failure after merge of the target-updates tree Stephen Rothwell
2015-10-07 12:27 ` [PATCH] stm class: Use per-attribute show and store methods in configfs policy Alexander Shishkin
2015-10-07 12:27 ` Alexander Shishkin [this message]
2015-10-07 20:22 ` linux-next: build failure after merge of the target-updates tree Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2015-06-03 8:16 Stephen Rothwell
2015-06-03 20:00 ` James Bottomley
2015-06-03 22:12 ` Nicholas A. Bellinger
2015-06-03 22:33 ` James Bottomley
2015-06-03 22:46 ` Nicholas A. Bellinger
2015-05-12 4:54 Stephen Rothwell
2014-10-03 5:46 Stephen Rothwell
2014-10-03 8:10 ` Nicholas A. Bellinger
2014-05-23 9:11 Stephen Rothwell
2014-05-23 17:38 ` Nicholas A. Bellinger
2014-01-20 5:25 Stephen Rothwell
2012-09-17 3:41 Stephen Rothwell
2012-09-18 0:57 ` Nicholas A. Bellinger
2012-02-10 0:50 Stephen Rothwell
2012-02-10 1:33 ` Nicholas A. Bellinger
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=87bncaj23e.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux$(echo .)intel.com \
--cc=arnd@arndb$(echo .)de \
--cc=greg@kroah$(echo .)com \
--cc=hch@lst$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nab@linux-iscsi$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/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