mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jaewon Kim <jaewon02.kim@samsung.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Andi Shyti <andi@etezian.org>,
	Alim Akhtar <alim.akhtar@samsung.com>
Subject: Re: [PATCH] spi: s3c64xx: add no_cs description
Date: Fri, 31 Mar 2023 10:07:32 +0900	[thread overview]
Message-ID: <886e1f40-79d3-3e5f-bc11-06ce4a04ccec@samsung.com> (raw)
In-Reply-To: <420495f8-b894-1665-bbc3-f5cab0f95301@linaro.org>

Hi Krzysztof


I always appreciate your kind guide.


I used 'get_maintainers.pl' but the Mark was missing.

Because the changes in this patch are only in 
"include/linux/platform_data/".

There was no touch in SPI driver. So, script did not outputting the SPI 
Maintainer.


Thanks

Jaewon Kim

On 23. 3. 30. 23:46, Krzysztof Kozlowski wrote:
> On 30/03/2023 15:40, Jaewon Kim wrote:
>> Hello Mark
>>
>>
>> Could you apply this patch?
>>
>> I missed you in the mail recipient.
>>
>>
>> https://protect2.fireeye.com/v1/url?k=62c6672d-034d7217-62c7ec62-74fe4860008a-45c729ef051007d6&q=1&e=03453742-6822-4fdc-9ee7-bdb6bdb0fe4f&u=https%3A%2F%2Flkml.org%2Flkml%2F2023%2F3%2F6%2F34
>>
>> https://protect2.fireeye.com/v1/url?k=41253bbb-20ae2e81-4124b0f4-74fe4860008a-f6ba8ee97b64390d&q=1&e=03453742-6822-4fdc-9ee7-bdb6bdb0fe4f&u=https%3A%2F%2Flkml.org%2Flkml%2F2023%2F3%2F6%2F232
> I think you should resend. This time with entire output of
> scripts/get_maintainers.pl
>
> Best regards,
> Krzysztof
>
>

  reply	other threads:[~2023-03-31  1:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230306015413epcas2p371356e4008af6978cdadb5b859d8be2a@epcas2p3.samsung.com>
2023-03-06  1:42 ` Jaewon Kim
2023-03-06  6:26   ` Krzysztof Kozlowski
2023-03-06  9:06   ` Andi Shyti
2023-03-30 13:40   ` Jaewon Kim
2023-03-30 14:46     ` Krzysztof Kozlowski
2023-03-31  1:07       ` Jaewon Kim [this message]
2023-03-30 19:59   ` Mark Brown

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=886e1f40-79d3-3e5f-bc11-06ce4a04ccec@samsung.com \
    --to=jaewon02.kim@samsung.com \
    --cc=alim.akhtar@samsung.com \
    --cc=andi@etezian.org \
    --cc=broonie@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-spi@vger.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®