All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Lisov <sleirsgoevy@gmail.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] devicetree: synopsys-dw-mshc-common: add "fifo-access-32bit" property
Date: Sat, 11 Mar 2023 18:57:18 +0100	[thread overview]
Message-ID: <640cc326.c20a0220.2dc43.0e1a@mx.google.com> (raw)
In-Reply-To: <4de11c0b-8e09-c3ef-4180-585662386859@linaro.org>

> Why did you remove the subject? Please keep the mailing process matching
> mailing lists. It messes with mailboxes, filters and reading process.

Sorry about this, I just wanted to get rid of those X-Something headers and
accidentially deleted this one.

> Yeah, Rob acked it so I will let him to judge this. To me it looks like
> unnecessary fragmentation - this looks like compatible specific, not
> board. Anyway you need to resend to fix all the mailing mess.
> 
> Best regards,
> Krzysztof

Should I resend the whole patchset from scratch, as if nothing happened?

  parent reply	other threads:[~2023-03-11 18:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 15:23 [PATCH 0/2] dw_mmc: fix DW MMC cores with 32-bit bus on 64-bit Linux systems Sergey Lisov
2023-03-11 15:22 ` [PATCH 1/2] devicetree: synopsys-dw-mshc-common: add "fifo-access-32bit" property Sergey Lisov
2023-03-11 15:50   ` Krzysztof Kozlowski
2023-03-11 17:40     ` Sergey Lisov
2023-03-11 17:40       ` Sergey Lisov
2023-03-11 17:40       ` Sergey Lisov
2023-03-11 17:57       ` broken subject? Krzysztof Kozlowski
2023-03-11 17:57         ` [PATCH 1/2] devicetree: synopsys-dw-mshc-common: add "fifo-access-32bit" property Sergey Lisov
2023-03-11 17:57         ` Sergey Lisov [this message]
2023-03-11 17:57         ` Sergey Lisov
2023-03-11 15:22 ` [PATCH 2/2] dw_mmc: add an option to force 32-bit accesses to 64-bit device registers Sergey Lisov
     [not found] <640cc323.050a0220.8e83b.0e60@mx.google.com>
2023-03-11 18:08 ` [PATCH 1/2] devicetree: synopsys-dw-mshc-common: add "fifo-access-32bit" property Krzysztof Kozlowski
     [not found] <640c80ff.050a0220.2983.0b8d@mx.google.com>
2023-03-11 15:58 ` Krzysztof Kozlowski
  -- strict thread matches above, loose matches on Subject: below --
2023-03-11 12:54 Sergey Lisov
2023-03-11 12:54 Sergey Lisov
2023-03-11 12:54 Sergey Lisov

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=640cc326.c20a0220.2dc43.0e1a@mx.google.com \
    --to=sleirsgoevy@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jh80.chung@samsung.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=ulf.hansson@linaro.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.