linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@fifo99.com>
To: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Daniel Walker <danielwa@cisco.com>,
	Christophe Leroy <christophe.leroy@c-s.fr>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Rob Herring <robh+dt@kernel.org>,
	xe-linux-external@cisco.com, linuxppc-dev@lists.ozlabs.org,
	Maksym Kokhan <maksym.kokhan@globallogic.com>,
	linux-kernel@vger.kernel.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/4] add generic builtin command line
Date: Tue, 16 Feb 2021 11:02:26 -0800	[thread overview]
Message-ID: <20210216190226.GY22125@fifo99.com> (raw)
In-Reply-To: <1613417521.3853.5.camel@chimera>

On Mon, Feb 15, 2021 at 11:32:01AM -0800, Daniel Gimpelevich wrote:
> On Thu, 2019-03-21 at 15:15 -0700, Andrew Morton wrote:
> > On Thu, 21 Mar 2019 08:13:08 -0700 Daniel Walker <danielwa@cisco.com> wrote:
> > > On Wed, Mar 20, 2019 at 08:14:33PM -0700, Andrew Morton 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.
> 
> This patchset is currently neither in mainline nor in -next. May I ask
> what happened to it? Thanks.
> 

It was dropped silently by Andrew at some point. I wasn't watching -next closely
to know when. I have no idea why he dropped it.

We still use this series extensively in Cisco, and have extended it beyond this
current series.

We can re-submit.

Daniel

  parent reply	other threads:[~2021-02-16 19:12 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
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 [this message]
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=20210216190226.GY22125@fifo99.com \
    --to=dwalker@fifo99.com \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=christophe.leroy@c-s.fr \
    --cc=daniel@gimpelevich.san-francisco.ca.us \
    --cc=danielwa@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maksym.kokhan@globallogic.com \
    --cc=mpe@ellerman.id.au \
    --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).