From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
"linux-um@lists.infradead.org" <linux-um@lists.infradead.org>,
Alex Gaynor <alex.gaynor@gmail.com>,
Geoffrey Thomas <geofft@ldpreload.com>,
Finn Behrens <me@kloenk.de>,
Adam Bratschi-Kaye <ark.email@gmail.com>,
Wedson Almeida Filho <wedsonaf@google.com>,
Boqun Feng <boqun.feng@gmail.com>,
Sumera Priyadarsini <sylphrenadin@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Sven Van Asbroeck <thesven73@gmail.com>,
Gary Guo <gary@garyguo.net>,
Boris-Chengbiao Zhou <bobo1239@web.de>,
Fox Chen <foxhlchen@gmail.com>,
Ayaan Zaidi <zaidi.ayaan@gmail.com>,
Douglas Su <d0u9.su@outlook.com>, Yuki Okushi <jtitor@2k36.org>
Subject: Re: linux-next: Tree for Oct 18 ('make' error on ARCH=um)
Date: Wed, 20 Oct 2021 16:48:58 +0200 [thread overview]
Message-ID: <CANiq72=zBuRWdYQBE=i_pmv57QS7ZGNKZzL2wegNYeB=4G-JyQ@mail.gmail.com> (raw)
In-Reply-To: <b0eddd67-e62f-c6c3-37d1-8c69f27c51fb@infradead.org>
On Wed, Oct 20, 2021 at 4:46 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> Stephen, Miguel,
>
> No problems like this in linux-next 2021-10-20.
>
> thanks.
Thanks for the confirmation and apologies for the issue.
Cheers,
Miguel
next prev parent reply other threads:[~2021-10-20 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 9:30 linux-next: Tree for Oct 18 Stephen Rothwell
2021-10-18 21:14 ` linux-next: Tree for Oct 18 ('make' error on ARCH=um) Randy Dunlap
2021-10-18 21:58 ` Stephen Rothwell
2021-10-18 22:18 ` Miguel Ojeda
2021-10-20 4:56 ` Stephen Rothwell
2021-10-20 14:23 ` Randy Dunlap
2021-10-20 14:46 ` Randy Dunlap
2021-10-20 14:48 ` Miguel Ojeda [this message]
2021-10-20 20:59 ` 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='CANiq72=zBuRWdYQBE=i_pmv57QS7ZGNKZzL2wegNYeB=4G-JyQ@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=ark.email@gmail.com \
--cc=bobo1239@web.de \
--cc=boqun.feng@gmail.com \
--cc=d0u9.su@outlook.com \
--cc=foxhlchen@gmail.com \
--cc=gary@garyguo.net \
--cc=geofft@ldpreload.com \
--cc=jtitor@2k36.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=me@kloenk.de \
--cc=mpe@ellerman.id.au \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=sylphrenadin@gmail.com \
--cc=thesven73@gmail.com \
--cc=wedsonaf@google.com \
--cc=zaidi.ayaan@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).