From: Russell Currey <ruscur@russell.cc>
To: "Murilo Opsfelder Araújo" <mopsfelder@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Cc: joel@jms.id.au, npiggin@gmail.com
Subject: Re: [PATCH] powerpc/powernv: Get more flushing requirements from device-tree
Date: Mon, 04 Apr 2022 20:11:40 +1000 [thread overview]
Message-ID: <0c9c0f9e2030abfe60f24a7050437f7bd1c76e19.camel@russell.cc> (raw)
In-Reply-To: <bbbd59a9-c93a-0bb4-6131-1b769f257094@gmail.com>
On Wed, 2022-03-23 at 16:26 -0300, Murilo Opsfelder Araújo wrote:
> Hi, Russell.
>
> I think this patch could have been split in half with their
> corresponding Fixes: tag.
>
> This may sound nitpicking but doing this would certainly help distros
> doing their backports.
Hi Murilo,
I didn't use the Fixes: tag originally since as far as I'm aware this
issue doesn't impact any systems "out in the wild" - so I didn't think
there would be interest in any backports. I should have split and
tagged the commits anyway though, in case others wanted to make that
decision.
Will resend.
prev parent reply other threads:[~2022-04-04 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 7:47 [PATCH] powerpc/powernv: Get more flushing requirements from device-tree Russell Currey
2022-03-23 19:26 ` Murilo Opsfelder Araújo
2022-04-04 10:11 ` Russell Currey [this message]
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=0c9c0f9e2030abfe60f24a7050437f7bd1c76e19.camel@russell.cc \
--to=ruscur@russell.cc \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mopsfelder@gmail.com \
--cc=npiggin@gmail.com \
/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).