All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Roger Quadros <rogerq@kernel.org>
Cc: "Brock.Zheng" <yzheng@techyauld.com>,
	Tony Lindgren <tony@atomide.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memory: omap-gpmc: fixup wrongly hierarchy of the sub-devices
Date: Fri, 1 Mar 2024 13:38:09 +0100	[thread overview]
Message-ID: <20240301133809.0d26865e@aktux> (raw)
In-Reply-To: <f45b3195-38a9-4c49-b873-01e5a0b275a3@kernel.org>

Hi,

On Fri, 1 Mar 2024 13:22:12 +0200
Roger Quadros <rogerq@kernel.org> wrote:

> Hi,
> 
> Thanks for the patch but can you please re-send the patch in plain text format?
> Please refer to this article for more details.
> 
> https://subspace.kernel.org/etiquette.html
> 
for my own education, can you specify against what the patch excactly offends?
I see no html there and

Content-Type: text/plain; charset=gb2312

So what do you consider not "plain" in that email?

Regards,
Andreas

  reply	other threads:[~2024-03-01 12:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 23:52 [PATCH] memory: omap-gpmc: fixup wrongly hierarchy of the sub-devices Brock.Zheng
2024-03-01 11:22 ` Roger Quadros
2024-03-01 12:38   ` Andreas Kemnade [this message]
2024-03-01 13:41     ` Roger Quadros
2024-03-01 23:57       ` [PATCH] memory/omap-gpmc: " Brock Zheng
2024-03-02 16:25         ` Krzysztof Kozlowski
     [not found]         ` <beacb55c-951b-4177-83ab-94fda44cd2b7@kernel.org>
2024-03-03  8:18           ` [PATCH] memory: omap-gpmc: " Brock Zheng
2024-03-05  9:55             ` Roger Quadros
2024-03-08 16:48             ` Krzysztof Kozlowski
2024-03-26  9:09               ` Krzysztof Kozlowski
2024-03-01 11:40 ` Krzysztof Kozlowski

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=20240301133809.0d26865e@aktux \
    --to=andreas@kemnade.info \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rogerq@kernel.org \
    --cc=tony@atomide.com \
    --cc=yzheng@techyauld.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 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.