From: Andrew Morton <akpm@linux-foundation.org>
To: Daniel Walker <danielwa@cisco.com>
Cc: Maksym Kokhan <maksym.kokhan@globallogic.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Paul Mackerras <paulus@samba.org>,
xe-linux-external@cisco.com, Daniel Walker <dwalker@fifo99.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/4] add generic builtin command line
Date: Thu, 21 Mar 2019 15:15:19 -0700 [thread overview]
Message-ID: <20190321151519.1f4479d92228c8a8738e02cf@linux-foundation.org> (raw)
In-Reply-To: <20190321151308.yt6uc3mxgppm5zko@zorba>
On Thu, 21 Mar 2019 08:13:08 -0700 Daniel Walker <danielwa@cisco.com> wrote:
> > The patches (or some version of them) are already in linux-next,
> > which messes me up. I'll disable them for now.
>
> Those are from my tree, but I remove them when you picked up the series. The
> next linux-next should not have them.
Yup, thanks, all looks good now.
next prev parent reply other threads:[~2019-03-21 22:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 23:24 [PATCH 1/4] add generic builtin command line Daniel Walker
2019-03-20 22:53 ` Andrew Morton
2019-03-20 23:23 ` Daniel Walker
2019-03-21 3:14 ` Andrew Morton
2019-03-21 15:13 ` Daniel Walker
2019-03-21 22:15 ` Andrew Morton [this message]
2021-02-15 19:32 ` Daniel Gimpelevich
2021-02-16 17:42 ` Christophe Leroy
2021-02-16 21:20 ` Daniel Gimpelevich
2021-02-16 19:02 ` Daniel Walker
2021-02-17 21:16 ` Andrew Morton
2023-04-17 16:18 ` Tomas Mudrunka
2023-04-17 16:24 ` Daniel Walker (danielwa)
2023-10-17 10:40 ` Pratyush Brahma
2023-10-17 14:21 ` Daniel Walker (danielwa)
2023-10-19 6:43 ` Pratyush Brahma
2023-11-08 11:33 ` Christophe Leroy
2023-11-08 16:23 ` Daniel Walker (danielwa)
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=20190321151519.1f4479d92228c8a8738e02cf@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=danielwa@cisco.com \
--cc=dwalker@fifo99.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maksym.kokhan@globallogic.com \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.org \
--cc=xe-linux-external@cisco.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).