From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: broonie@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org
Subject: Re: mmotm 2022-01-26-21-04 uploaded
Date: Wed, 26 Jan 2022 22:02:06 -0800 [thread overview]
Message-ID: <20220126220206.2ec57a68c5a803818adbc816@linux-foundation.org> (raw)
In-Reply-To: <20220127165110.55e88e44@canb.auug.org.au>
On Thu, 27 Jan 2022 16:51:10 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Andrew,
>
> On Wed, 26 Jan 2022 21:04:56 -0800 akpm@linux-foundation.org wrote:
> >
> > * docs-sysctl-kernel-add-missing-bit-to-panic_print.patch
> > * panic-add-option-to-dump-all-cpus-backtraces-in-panic_print.patch
> > * panic-allow-printing-extra-panic-information-on-kdump.patch
>
>
> > * sysctl-documentation-fix-table-format-warning.patch
>
> Just wondering why this patch isn't up just after the above patches
> (instead of being in the post-next section)?
Dependencies are all over the place and are moving around. Now fixed
up, thanks.
next prev parent reply other threads:[~2022-01-27 6:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 5:04 mmotm 2022-01-26-21-04 uploaded akpm
2022-01-27 5:51 ` Stephen Rothwell
2022-01-27 6:02 ` Andrew Morton [this message]
2022-01-27 6:31 ` mmotm 2022-01-26-21-04 uploaded (drivers/mtd/nand.raw/Kconfig warning) Randy Dunlap
2022-01-27 6:52 ` mmotm 2022-01-26-21-04 uploaded (gpu/drm/i915/i915_gem_evict.h) Randy Dunlap
2022-01-27 9:44 ` Jani Nikula
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=20220126220206.2ec57a68c5a803818adbc816@linux-foundation.org \
--to=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;
as well as URLs for NNTP newsgroup(s).