linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Stephen Rothwell <sfr@rothwell.id.au>
Cc: Liam Howlett <liam.howlett@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"maple-tree@lists.infradead.org" <maple-tree@lists.infradead.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Maple Tree for next
Date: Wed, 16 Feb 2022 21:21:48 +0000	[thread overview]
Message-ID: <Yg1q7K7ZHOBUg+eo@casper.infradead.org> (raw)
In-Reply-To: <20220217080426.2fdabf7e@elm.ozlabs.ibm.com>

On Thu, Feb 17, 2022 at 08:04:26AM +1100, Stephen Rothwell wrote:
> Hi Liam,
> 
> On Wed, 16 Feb 2022 19:14:53 +0000 Liam Howlett <liam.howlett@oracle.com> wrote:
> >
> > Please include a new tree in linux-next:
> > 
> > https://github.com/oracle/linux-uek/tree/mainline/maple
> > Aka
> > https://github.com/oracle/linux-uek.git mainline/maple
> 
> That does no exist :-(

Transposition; the correct URL is:

https://github.com/oracle/linux-uek.git maple/mainline

> Please tell me something about you (I can't find you in the MAINTAINERS
> file) and this tree i.e. what it will contain, its path to Linus' tree
> (direct or via another tree).

I'll let Liam answer these questions himself :-)




  reply	other threads:[~2022-02-16 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 19:14 Maple Tree for next Liam Howlett
2022-02-16 21:04 ` Stephen Rothwell
2022-02-16 21:21   ` Matthew Wilcox [this message]
2022-02-17  2:07     ` Liam Howlett
2022-02-17  6:31       ` Stephen Rothwell

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=Yg1q7K7ZHOBUg+eo@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=liam.howlett@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=maple-tree@lists.infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sfr@rothwell.id.au \
    --cc=torvalds@linux-foundation.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 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).