From: Florian Fainelli <f.fainelli@gmail.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Mike Kravetz" <mike.kravetz@oracle.com>,
"Doug Berger" <opendmb@gmail.com>,
"Michal Hocko" <mhocko@kernel.org>,
"SeongJae Park" <sj@kernel.org>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Mike Rapoport" <rppt@linux.ibm.com>,
"Vlastimil Babka" <vbabka@suse.cz>
Subject: Re: Updated git tree for MM patches??
Date: Thu, 3 Feb 2022 08:31:52 -0800 [thread overview]
Message-ID: <80777e3c-385c-d481-167b-c3491273019f@gmail.com> (raw)
In-Reply-To: <Yfvn2gatF0NA1ihp@cmpxchg.org>
On 2/3/2022 6:34 AM, Johannes Weiner wrote:
> Hi Florian,
>
> On Wed, Feb 02, 2022 at 04:21:38PM -0800, Florian Fainelli wrote:
>> Hi Andrew, Johannes,
>>
>> The MAINTAINERS file for MEMORY MANAGEMENT lists the following git tree:
>>
>> git://github.com/hnaz/linux-mm.git
>>
>> however it does not look like it has been updated in the past 5 months or so
>> as master still points to 5.17-rc7-mm1
>
> Oops, that was a bug in my script. I had to work around a behavior
> change in wget and it looks like it started failing quietly in the
> next wget version.
>
> All fixed now and the tree is uptodate again. Thanks for the report.
And thank you for fixing it quickly, looking good now!
--
Florian
prev parent reply other threads:[~2022-02-03 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 0:21 Updated git tree for MM patches?? Florian Fainelli
2022-02-03 7:01 ` Mike Rapoport
2022-02-03 9:52 ` Vlastimil Babka
2022-02-03 8:52 ` SeongJae Park
2022-02-03 14:34 ` Johannes Weiner
2022-02-03 16:31 ` Florian Fainelli [this message]
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=80777e3c-385c-d481-167b-c3491273019f@gmail.com \
--to=f.fainelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=opendmb@gmail.com \
--cc=rppt@linux.ibm.com \
--cc=sj@kernel.org \
--cc=vbabka@suse.cz \
/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.