public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Evgeniy Polyakov <zbr@ioremap.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	soc@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 12/15] w1: omap-hdq: allow compile testing
Date: Sun, 16 Apr 2023 09:22:08 +0200	[thread overview]
Message-ID: <9e7ccb2c-265b-befb-ceaa-30fb4d0e379e@linaro.org> (raw)
In-Reply-To: <f5683efc-733e-a5ee-b3ba-6b35e04e23b4@infradead.org>

On 15/04/2023 18:05, Randy Dunlap wrote:
> Hi,
> 
> On 4/15/23 03:43, Krzysztof Kozlowski wrote:
>> omap-hdq does not depend on anything from ARCH_OMAP for building.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> 
> It appears that patches 4 and 12 are the same...

Yes, I messed with git format-patch a bit. #4 can be ignored.

Best regards,
Krzysztof


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-04-16  7:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-15 10:42 [PATCH 01/15] w1: ds2408: drop kerneldoc annotation Krzysztof Kozlowski
2023-04-15 10:42 ` [PATCH 02/15] w1: ds2433: correct " Krzysztof Kozlowski
2023-04-15 16:08   ` Randy Dunlap
2023-04-15 10:42 ` [PATCH 03/15] w1: ds28e04: " Krzysztof Kozlowski
2023-04-15 16:07   ` Randy Dunlap
2023-04-15 10:42 ` [PATCH 04/15] w1: minor white-space and code style fixes Krzysztof Kozlowski
2023-04-15 10:42 ` [PATCH 4/4] w1: omap-hdq: allow compile testing Krzysztof Kozlowski
2023-04-15 15:18   ` Greg Kroah-Hartman
2023-04-16  7:18     ` Krzysztof Kozlowski
2023-04-15 10:42 ` [PATCH 05/15] w1: use octal for file permissions Krzysztof Kozlowski
2023-04-15 10:42 ` [PATCH 06/15] w1: ds2433: do not use assignment in if condition Krzysztof Kozlowski
2023-04-15 10:42 ` [PATCH 07/15] w1: ds2482: drop unnecessary header Krzysztof Kozlowski
2023-04-15 10:42 ` [PATCH 08/15] w1: ds2482: do not use assignment in if condition Krzysztof Kozlowski
2023-04-15 10:42 ` [PATCH 09/15] w1: matrox: switch from asm to linux header Krzysztof Kozlowski
2023-04-15 10:42 ` [PATCH 10/15] w1: matrox: use inline over __inline__ Krzysztof Kozlowski
2023-04-15 10:43 ` [PATCH 11/15] w1: matrox: remove unnecessary ENOMEM messages Krzysztof Kozlowski
2023-04-15 10:43 ` [PATCH 12/15] w1: omap-hdq: allow compile testing Krzysztof Kozlowski
2023-04-15 16:05   ` Randy Dunlap
2023-04-16  7:22     ` Krzysztof Kozlowski [this message]
2023-04-15 10:43 ` [PATCH 13/15] w1: omap-hdq: add SPDX tag Krzysztof Kozlowski
2023-04-15 10:43 ` [PATCH 14/15] w1: omap-hdq: remove unnecessary ENOMEM messages Krzysztof Kozlowski
2023-04-15 10:43 ` [PATCH 15/15] w1: gpio: " Krzysztof Kozlowski
2023-04-15 16:07 ` [PATCH 01/15] w1: ds2408: drop kerneldoc annotation Randy Dunlap

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=9e7ccb2c-265b-befb-ceaa-30fb4d0e379e@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=rdunlap@infradead.org \
    --cc=soc@kernel.org \
    --cc=zbr@ioremap.net \
    /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