From: Richard Weinberger <richard@nod.at>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Jeff Dike <jdike@addtoit.com>,
x86@kernel.org, linux-um@lists.infradead.org,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Andy Lutomirski <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/2] x86/build/vdso: a little more Makefile cleanups
Date: Tue, 03 Jul 2018 09:20:20 +0200 [thread overview]
Message-ID: <2251685.NraJYuIFmt@blindfold> (raw)
In-Reply-To: <1530582614-5173-1-git-send-email-yamada.masahiro@socionext.com>
Masahiro,
Am Dienstag, 3. Juli 2018, 03:50:12 CEST schrieb Masahiro Yamada:
>
> At first, I sent the first patch to UML ML,
> but they did not pick it up.
> Instead, I was able to get Acked-by from Richard,
> one of the UML maintainers.
>
> https://patchwork.kernel.org/patch/10399787/
>
> I am resending it to x86 ML.
Uhh, I thought you want to carry this via your tree?
I don't mind picking up these patches.
Thanks,
//richard
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard@nod.at>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-um@lists.infradead.org, linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@kernel.org>, Jeff Dike <jdike@addtoit.com>
Subject: Re: [PATCH 0/2] x86/build/vdso: a little more Makefile cleanups
Date: Tue, 03 Jul 2018 09:20:20 +0200 [thread overview]
Message-ID: <2251685.NraJYuIFmt@blindfold> (raw)
In-Reply-To: <1530582614-5173-1-git-send-email-yamada.masahiro@socionext.com>
Masahiro,
Am Dienstag, 3. Juli 2018, 03:50:12 CEST schrieb Masahiro Yamada:
>
> At first, I sent the first patch to UML ML,
> but they did not pick it up.
> Instead, I was able to get Acked-by from Richard,
> one of the UML maintainers.
>
> https://patchwork.kernel.org/patch/10399787/
>
> I am resending it to x86 ML.
Uhh, I thought you want to carry this via your tree?
I don't mind picking up these patches.
Thanks,
//richard
next prev parent reply other threads:[~2018-07-03 7:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 1:50 [PATCH 0/2] x86/build/vdso: a little more Makefile cleanups Masahiro Yamada
2018-07-03 1:50 ` [PATCH 1/2] x86/build/vdso: remove unused vdso-syms.lds Masahiro Yamada
2018-07-03 1:50 ` Masahiro Yamada
2018-07-03 7:52 ` [tip:x86/asm] x86/build/vdso: Remove " tip-bot for Masahiro Yamada
2018-07-03 1:50 ` [PATCH 2/2] x86/build/vdso: simplify cmd_vdso2c Masahiro Yamada
2018-07-03 7:52 ` [tip:x86/asm] x86/build/vdso: Simplify 'cmd_vdso2c' tip-bot for Masahiro Yamada
2018-07-03 7:20 ` Richard Weinberger [this message]
2018-07-03 7:20 ` [PATCH 0/2] x86/build/vdso: a little more Makefile cleanups Richard Weinberger
2018-07-03 7:35 ` Ingo Molnar
2018-07-03 7:37 ` Masahiro Yamada
2018-07-03 7:49 ` Richard Weinberger
2018-07-03 7:57 ` Ingo Molnar
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=2251685.NraJYuIFmt@blindfold \
--to=richard@nod.at \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.