From: Johannes Berg <johannes@sipsolutions.net>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Randy Dunlap <rdunlap@infradead.org>,
David Gow <davidgow@google.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kbuild@vger.kernel.org, Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
linux-um <linux-um@lists.infradead.org>,
x86@kernel.org
Subject: Re: [PATCH] um: Add missing "FORCE" target when using if_changed
Date: Sat, 09 Oct 2021 15:06:01 +0200 [thread overview]
Message-ID: <5B27741E-71A5-41CF-912C-D299248691F7@sipsolutions.net> (raw)
In-Reply-To: <f0ead035-f05b-73fb-1fd4-48c1eff8bc92@cambridgegreys.com>
On 9 October 2021 07:36:36 CEST, Anton Ivanov <anton.ivanov@cambridgegreys.com> wrote:
>The patch by Johannes is not in the pending list in patchwork, so it
>looks like Richard has processed it and it will be in the next pull request.
I think it's still open: https://patchwork.ozlabs.org/project/linux-um/patch/20210928115146.277bec2328bb.If70926505d16d6c6a229002eb6d3f6838b546175@changeid/
johannes
--
Sent from my phone.
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Randy Dunlap <rdunlap@infradead.org>,
David Gow <davidgow@google.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kbuild@vger.kernel.org, Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
linux-um <linux-um@lists.infradead.org>,
x86@kernel.org
Subject: Re: [PATCH] um: Add missing "FORCE" target when using if_changed
Date: Sat, 09 Oct 2021 15:06:01 +0200 [thread overview]
Message-ID: <5B27741E-71A5-41CF-912C-D299248691F7@sipsolutions.net> (raw)
In-Reply-To: <f0ead035-f05b-73fb-1fd4-48c1eff8bc92@cambridgegreys.com>
On 9 October 2021 07:36:36 CEST, Anton Ivanov <anton.ivanov@cambridgegreys.com> wrote:
>The patch by Johannes is not in the pending list in patchwork, so it
>looks like Richard has processed it and it will be in the next pull request.
I think it's still open: https://patchwork.ozlabs.org/project/linux-um/patch/20210928115146.277bec2328bb.If70926505d16d6c6a229002eb6d3f6838b546175@changeid/
johannes
--
Sent from my phone.
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2021-10-09 13:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 21:51 [PATCH] um: Add missing "FORCE" target when using if_changed Randy Dunlap
2021-10-08 21:51 ` Randy Dunlap
2021-10-08 23:23 ` David Gow
2021-10-08 23:23 ` David Gow
2021-10-09 0:01 ` Randy Dunlap
2021-10-09 0:01 ` Randy Dunlap
2021-10-09 5:36 ` Anton Ivanov
2021-10-09 5:36 ` Anton Ivanov
2021-10-09 13:06 ` Johannes Berg [this message]
2021-10-09 13:06 ` Johannes Berg
2021-10-09 20:20 ` Richard Weinberger
2021-10-09 20:20 ` Richard Weinberger
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=5B27741E-71A5-41CF-912C-D299248691F7@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=davidgow@google.com \
--cc=jdike@addtoit.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=x86@kernel.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 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.