From: Chris Packham <Chris.Packham@alliedtelesis.co.nz> To: "email@example.com" <firstname.lastname@example.org> Cc: "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org> Subject: Re: [PATCH v9 1/8] ARM: aurora-l2: add prefix to MAX_RANGE_SIZE Date: Tue, 27 Aug 2019 21:13:11 +0000 Message-ID: <email@example.com> (raw) In-Reply-To: <20190827210713.GO13294@shell.armlinux.org.uk> On Tue, 2019-08-27 at 22:07 +0100, Russell King - ARM Linux admin wrote: > On Tue, Aug 27, 2019 at 08:56:05PM +0000, Chris Packham wrote: > > On Tue, 2019-08-27 at 10:13 +0100, Russell King - ARM Linux admin > > wrote: > > > Just send the single patch to the patch tracker - having it against > > > 5.3-rc is fine (I don't think anything has changed for a long time > > > with that file.) > > > > Done > > https://www.armlinux.org.uk/developer/patches/viewpatch.php?id=8902/1 > > > > I'm still not entirely sure what to put for the KernelVersion tag. In > > hindsight think I misinterpreted your comment above and set it to 5.3rc > > (where you meant a series based on 5.3-rcX should apply cleanly). It > > probably should have been next or master because it's way past the > > merge window for 5.3. > > Think about it as "which kernel version was _this_ patch generated > against" - it's a guide for me to know which kernel version it > should be applied to. The nearest Linus release (rc or final) is > generally sufficient. > > If it doesn't apply to my current base, then I might check out that > version, apply it there, and then merge it in, resolving any > conflicts during the merge. > > It started off with a different purpose: when we had the older > development system, such as the 2.x series kernels, we would have > even x being the current stable kernels, and concurrently we'd > also have x+1 as the development series. When someone sent me a > patch back then, it was important to know which kernel series it > was meant for. > > I decided not to get rid of it because it provides useful > information when patches don't apply, and gives more options > than me just discarding the patch with a comment saying it > doesn't apply. > Thanks for the info. So 5.3-rc is not as wrong as I thought it was. One could even summarize the above as. git format-patch --add-header \ "KernelVersion: $(git describe --abbrev=0 HEAD)"
next prev parent reply index Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-12 3:48 [PATCH v9 0/8] EDAC drivers for Armada XP L2 and DDR Chris Packham 2019-07-12 3:48 ` [PATCH v9 1/8] ARM: aurora-l2: add prefix to MAX_RANGE_SIZE Chris Packham 2019-08-23 10:46 ` Russell King - ARM Linux admin 2019-08-23 10:50 ` Russell King - ARM Linux admin 2019-08-26 0:46 ` Chris Packham 2019-08-27 9:13 ` Russell King - ARM Linux admin 2019-08-27 20:56 ` Chris Packham 2019-08-27 21:07 ` Russell King - ARM Linux admin 2019-08-27 21:13 ` Chris Packham [this message] 2019-08-27 21:15 ` Russell King - ARM Linux admin 2019-07-12 3:48 ` [PATCH v9 2/8] ARM: aurora-l2: add defines for parity and ECC registers Chris Packham 2019-07-12 3:48 ` [PATCH v9 3/8] ARM: l2x0: support parity-enable/disable on aurora Chris Packham 2019-07-12 3:49 ` [PATCH v9 4/8] dt-bindings: ARM: document marvell,ecc-enable binding Chris Packham 2019-07-12 3:49 ` [PATCH v9 5/8] ARM: l2x0: add marvell,ecc-enable property for aurora Chris Packham 2019-07-12 3:49 ` [PATCH v9 6/8] EDAC: Add missing debugfs_create_x32 wrapper Chris Packham 2019-07-12 3:49 ` [PATCH v9 7/8] EDAC: Add driver for the Marvell Armada XP SDRAM and L2 cache ECC Chris Packham 2019-07-12 3:49 ` [PATCH v9 8/8] EDAC: armada_xp: Add support for more SoCs Chris Packham 2019-07-26 14:51 ` James Morse 2019-07-28 20:52 ` Chris Packham 2019-07-26 14:53 ` [PATCH v9 0/8] EDAC drivers for Armada XP L2 and DDR James Morse 2019-07-28 20:33 ` Chris Packham
Reply instructions: You may reply publically 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
Linux-EDAC Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-edac/0 linux-edac/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-edac linux-edac/ https://lore.kernel.org/linux-edac \ email@example.com firstname.lastname@example.org public-inbox-index linux-edac Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-edac AGPL code for this site: git clone https://public-inbox.org/ public-inbox