From: Anshuman Khandual <anshuman.khandual@arm.com>
To: akpm@linux-foundation.org, broonie@kernel.org, mhocko@suse.cz,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org
Subject: Re: mmotm 2018-12-21-15-28 uploaded
Date: Mon, 7 Jan 2019 13:02:31 +0530 [thread overview]
Message-ID: <99ab6512-9fce-9cb9-76e7-7f83d87d5f86@arm.com> (raw)
In-Reply-To: <20181221232853.WLvEi%akpm@linux-foundation.org>
On 12/22/2018 04:58 AM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2018-12-21-15-28 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
> You will need quilt to apply these patches to the latest Linus release (4.x
> or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> http://ozlabs.org/~akpm/mmotm/series
>
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
>
> This tree is partially included in linux-next. To see which patches are
> included in linux-next, consult the `series' file. Only the patches
> within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> linux-next.
>
> A git tree which contains the memory management portion of this tree is
> maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.gi
Hello Michal,
I dont see the newer tags on this tree. Tried fetching all the tags from the tree
but only see these right now for 2018. This release should have an equivalent tag
(mmotm-2018-12-21-15-28) right ?
mmotm-2018-01-04-16-19
mmotm-2018-01-12-16-53
mmotm-2018-01-18-16-31
mmotm-2018-01-25-16-20
mmotm-2018-01-31-16-51
mmotm-2018-02-06-16-41
mmotm-2018-02-21-14-48
mmotm-2018-03-13-15-15
mmotm-2018-03-14-16-24
mmotm-2018-03-22-16-18
mmotm-2018-03-28-16-05
mmotm-2018-04-05-16-59
mmotm-2018-04-10-17-02
mmotm-2018-04-13-17-28
mmotm-2018-05-03-15-54
mmotm-2018-05-10-16-34
mmotm-2018-05-18-16-44
mmotm-2018-05-25-14-52
- Anshuman
next prev parent reply other threads:[~2019-01-07 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 23:28 akpm
2019-01-07 7:32 ` Anshuman Khandual [this message]
2019-01-07 8:43 ` Michal Hocko
2019-01-07 9:16 ` Anshuman Khandual
2019-01-07 9:23 ` Michal Hocko
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=99ab6512-9fce-9cb9-76e7-7f83d87d5f86@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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