From: Mike Rapoport <rppt@linux.ibm.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Stephen Boyd <sboyd@kernel.org>,
Kevin Cernekee <cernekee@gmail.com>,
Doug Berger <opendmb@gmail.com>,
Gregory Fong <gregory.0xf0@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build
Date: Tue, 26 May 2020 14:42:16 +0300 [thread overview]
Message-ID: <20200526114216.GI13212@linux.ibm.com> (raw)
In-Reply-To: <20200526111804.GW1551@shell.armlinux.org.uk>
On Tue, May 26, 2020 at 12:18:04PM +0100, Russell King - ARM Linux admin wrote:
> On Thu, May 21, 2020 at 11:18:23AM +0300, Mike Rapoport wrote:
> > (resendig for the correct address and with mailing list cc'ed, sorry for
> > the noise)
>
> There are two patches in the patch system, submitted within minutes
> of each other, with the same summary "Allow either FLATMEM or
> SPARSEMEM on the multiplatform build" but the patch and commit messages
> are different. I guess the summary for one of the patches is wrong?
Oops, my mistake.
The patch 8979/1 should have "ARM: Remove redundant
ARCH_SPARSEMEM_DEFAULT setting" in its subject.
Sorry.
> --
> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up
--
Sincerely yours,
Mike.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-26 11:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 8:18 [PATCH 0/2] ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build Mike Rapoport
2020-05-21 8:18 ` [PATCH 1/2] ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting Mike Rapoport
2020-05-21 8:18 ` [PATCH 2/2] ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build Mike Rapoport
2020-05-21 12:03 ` [PATCH 0/2] " Russell King - ARM Linux admin
2020-05-21 12:33 ` Mike Rapoport
2020-05-21 14:07 ` Mike Rapoport
2020-05-21 14:50 ` Russell King - ARM Linux admin
2020-05-21 15:56 ` Mike Rapoport
2020-06-02 12:18 ` Geert Uytterhoeven
2020-06-02 12:22 ` Russell King - ARM Linux admin
2020-06-02 12:37 ` Geert Uytterhoeven
2020-06-02 12:56 ` Russell King - ARM Linux admin
2020-05-26 11:18 ` Russell King - ARM Linux admin
2020-05-26 11:42 ` Mike Rapoport [this message]
2020-05-26 11:46 ` Russell King - ARM Linux admin
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=20200526114216.GI13212@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=cernekee@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gregory.0xf0@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=opendmb@gmail.com \
--cc=sboyd@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 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.