linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: broonie@kernel.org
Cc: "Adam Bratschi-Kaye" <ark.email@gmail.com>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Antonio Terceiro" <antonio.terceiro@linaro.org>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Boris-Chengbiao Zhou" <bobo1239@web.de>,
	"Daniel Xu" <dxu@dxuuu.xyz>,
	"Dariusz Sosnowski" <dsosnowski@dsosnowski.pl>,
	"Douglas Su" <d0u9.su@outlook.com>, "Finn Behrens" <me@kloenk.de>,
	"Gary Guo" <gary@garyguo.net>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Martin Rodriguez Reboredo" <yakoyoku@gmail.com>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Sven Van Asbroeck" <thesven73@gmail.com>,
	"Wedson Almeida Filho" <wedsonaf@google.com>
Subject: Re: linux-next: manual merge of the rust tree with the kbuild tree
Date: Wed, 28 Sep 2022 19:16:34 +0200	[thread overview]
Message-ID: <CANiq72=9ns5DU0C6eacxLnMkNUqZXa_gP_x3KLBKof8dR3HNYw@mail.gmail.com> (raw)
In-Reply-To: <20220927181647.487727-1-broonie@kernel.org>

On Tue, Sep 27, 2022 at 8:16 PM <broonie@kernel.org> wrote:
>
> I fixed it up (see below) and can carry the fix as necessary. This

Build-tested it -- works, thanks!

Cheers,
Miguel

  reply	other threads:[~2022-09-28 17:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 18:16 linux-next: manual merge of the rust tree with the kbuild tree broonie
2022-09-28 17:16 ` Miguel Ojeda [this message]
2022-10-04 22:23 ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2022-09-26 23:12 broonie
2022-09-27 12:47 ` Miguel Ojeda
2022-09-12  7:41 Stephen Rothwell
2022-08-02 23:38 broonie
2022-08-03  9:28 ` Miguel Ojeda
2022-08-14 23:08 ` Stephen Rothwell
2022-04-05  3:14 Stephen Rothwell
2022-04-05  8:33 ` Miguel Ojeda
2022-03-17  6:02 Stephen Rothwell
2022-03-17  7:11 ` Miguel Ojeda
2022-01-17 23:51 Stephen Rothwell
2021-12-07  5:13 Stephen Rothwell
2021-12-03  5:20 Stephen Rothwell
2021-12-03  9:05 ` Miguel Ojeda
2021-10-15  7:24 Stephen Rothwell
2021-10-15 12:24 ` Miguel Ojeda
2021-10-28  9:09 ` Stephen Rothwell
2021-10-28 11:06   ` Miguel Ojeda
2021-10-06  5:46 Stephen Rothwell
2021-08-11  7:26 Stephen Rothwell
2021-08-11 17:04 ` Nick Desaulniers
2021-08-12  6:34   ` Stephen Rothwell
2021-03-29  7:32 Stephen Rothwell
2021-03-18  4:37 Stephen Rothwell
2021-03-18  5:04 ` Miguel Ojeda

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=9ns5DU0C6eacxLnMkNUqZXa_gP_x3KLBKof8dR3HNYw@mail.gmail.com' \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=alex.gaynor@gmail.com \
    --cc=antonio.terceiro@linaro.org \
    --cc=ark.email@gmail.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=bobo1239@web.de \
    --cc=boqun.feng@gmail.com \
    --cc=broonie@kernel.org \
    --cc=d0u9.su@outlook.com \
    --cc=dsosnowski@dsosnowski.pl \
    --cc=dxu@dxuuu.xyz \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=me@kloenk.de \
    --cc=mpe@ellerman.id.au \
    --cc=ojeda@kernel.org \
    --cc=thesven73@gmail.com \
    --cc=wedsonaf@google.com \
    --cc=yakoyoku@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).