From: Maxwell Bland <mbland@motorola.com>
To: linux-mm@kvack.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Ard Biesheuvel <ardb@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Maxwell Bland <mbland@motorola.com>,
Alexandre Ghiti <alexghiti@rivosinc.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ptdump: add intermediate directory support
Date: Tue, 30 Apr 2024 11:13:57 -0500 [thread overview]
Message-ID: <36faail77z762b6tnldswwe4yxbedx3gwi4n5reldwbkovb5kb@m5gz4a3yqxav> (raw)
In-Reply-To: <fik5ys53dbkpkl22o4s7sw7cxi6dqjcpm2f3kno5tyms73jm5y@buo4jsktsnrt>
On Tue, Apr 30, 2024 at 11:05:01AM GMT, Maxwell Bland wrote:
> v3:
> - Added tabulation to delineate entries
> - Fixed formatting issues with mailer and rebased to mm/linus
>
> v2:
> - Rebased onto linux-next/akpm (the incorrect branch)
Note that I am referring to
20240423121820.874441838-1-mbland@motorola.com
as the v1/v2 here.
The v1/v2 mailer malformatting will hopefully never happen again. I have
tested mailing this patch to myself and have confirmed it cleanly merges
to mm/linus. I ended up needing to compile mutt from scratch. ):
Also, I made these changes in order to compliment testing
20240220203256.31153-1-mbland@motorola.com
and
20240423095843.446565600-1-mbland@motorola.com
and figured they might be useful to include/merge before attempting to
merge the above more impactful changes.
next prev parent reply other threads:[~2024-04-30 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 16:05 Maxwell Bland
2024-04-30 16:13 ` Maxwell Bland [this message]
2024-05-01 12:07 ` Catalin Marinas
2024-05-01 14:32 ` Maxwell Bland
2024-05-08 11:20 ` Catalin Marinas
2024-05-08 15:29 ` Maxwell Bland
2024-06-18 15:03 ` Maxwell Bland
2024-05-21 16:54 ` Jesse Taube
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=36faail77z762b6tnldswwe4yxbedx3gwi4n5reldwbkovb5kb@m5gz4a3yqxav \
--to=mbland@motorola.com \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.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