mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Conor.Dooley@microchip.com, Markus.Elfring@web.de,
	alif.zakuan.yuslaimi@intel.com, kah.jing.lee@intel.com
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	catalin.marinas@arm.com, conor+dt@kernel.org,
	dinguyen@kernel.org, robh+dt@kernel.org, will@kernel.org
Subject: Re: [PATCH v4] arm64: dts: agilex/stratix10: Updated QSPI Flash layout for UBIFS
Date: Mon, 3 Jul 2023 13:34:43 +0200	[thread overview]
Message-ID: <19a9fcdb-7ac9-c84f-56cc-940fe3548798@linaro.org> (raw)
In-Reply-To: <a786b6b9-3923-0138-5738-dc20e14aa0f3@microchip.com>

On 03/07/2023 11:08, Conor.Dooley@microchip.com wrote:
> On 03/07/2023 10:00, Markus Elfring wrote:
> 
>> …
>>> ---
>>> V4->V3: Drop cover letter & remove unnecessary marker line
>>> V3->V2: Update commit messages
>> …
>>
>> * Do you find the arrow notation helpful for the version identification?
>>
>> * How do you think about to avoid duplicate data in the version history?
>>
>> * Would an other listing style become nicer for the “patch changelog”?
> 
> This is a complete waste of contributor time. Please stop.

Markus is banned from the LKML. Just ignore the comments.

Best regards,
Krzysztof


  parent reply	other threads:[~2023-07-03 11:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  8:36 kah.jing.lee
     [not found] ` <59da2f49-706f-0a08-df14-71ad0326da83@web.de>
2023-07-03  9:08   ` Conor.Dooley
     [not found]     ` <b155011c-5e77-3e53-336c-53ad7d926f71@web.de>
2023-07-03 10:19       ` [v4] " Lee, Kah Jing
2023-07-03 11:34     ` Krzysztof Kozlowski [this message]
2023-07-10  2:21 ` [PATCH v4] " Dinh Nguyen

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=19a9fcdb-7ac9-c84f-56cc-940fe3548798@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=Conor.Dooley@microchip.com \
    --cc=Markus.Elfring@web.de \
    --cc=alif.zakuan.yuslaimi@intel.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=kah.jing.lee@intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --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

all inboxes | Powered by JetHome®