From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Doug Ledford <dledford@redhat.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Moni Shoua <monis@mellanox.com>, Kamal Heib <kamalh@mellanox.com>,
Amir Vadai <amirv@mellanox.com>,
Haggai Eran <haggaie@mellanox.com>,
Leon Romanovsky <leon@kernel.org>
Subject: Re: linux-next: build failure after merge of Linus' tree
Date: Tue, 9 Aug 2016 09:59:24 +1000 [thread overview]
Message-ID: <20160809095924.176c008b@canb.auug.org.au> (raw)
In-Reply-To: <a11851f5-067e-7b6d-6121-06e597381125@redhat.com>
Hi Doug,
On Mon, 8 Aug 2016 19:30:57 -0400 Doug Ledford <dledford@redhat.com> wrote:
>
> Doh! My apologies, that would certainly explain it. I'll reset my
> for-next tag.
Thanks.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-08-08 23:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 1:58 linux-next: build failure after merge of Linus' tree Stephen Rothwell
2016-08-08 15:37 ` Doug Ledford
2016-08-08 21:53 ` Stephen Rothwell
2016-08-08 23:30 ` Doug Ledford
2016-08-08 23:59 ` Stephen Rothwell [this message]
2016-08-09 8:54 ` Leon Romanovsky
2016-08-09 12:45 ` Doug Ledford
-- strict thread matches above, loose matches on Subject: below --
2025-02-03 1:59 Stephen Rothwell
2025-02-03 2:56 ` Jens Axboe
2024-09-26 0:04 Stephen Rothwell
2024-09-26 7:36 ` Alice Ryhl
2024-09-26 8:13 ` Stephen Rothwell
2024-09-26 8:24 ` Miguel Ojeda
2024-09-26 12:49 ` Sedat Dilek
2024-09-26 12:58 ` Miguel Ojeda
2024-09-26 14:44 ` Sedat Dilek
2024-09-26 14:57 ` Miguel Ojeda
2020-04-20 11:35 Stephen Rothwell
2015-10-07 22:44 Stephen Rothwell
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=20160809095924.176c008b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=amirv@mellanox.com \
--cc=dledford@redhat.com \
--cc=haggaie@mellanox.com \
--cc=kamalh@mellanox.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=monis@mellanox.com \
--cc=torvalds@linux-foundation.org \
/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