From: Arnd Bergmann <arnd@kernel.org>
To: Eugen Hristev <Eugen.Hristev@microchip.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Nicolas Ferre <Nicolas.Ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <Ludovic.Desroches@microchip.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Arnd Bergmann <arnd@arndb.de>,
tomi.valkeinen@ideasonboard.com,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] media: atmel: atmel-isc: fix build failures after split
Date: Thu, 22 Jul 2021 13:45:22 +0200 [thread overview]
Message-ID: <CAK8P3a0xp9BxwSt9+WTngsb1K12NGkroBwEf9p5Wg0Knf5umNQ@mail.gmail.com> (raw)
In-Reply-To: <BN9PR11MB5514AA62DD0F2A65828E62D6E8E49@BN9PR11MB5514.namprd11.prod.outlook.com>
On Thu, Jul 22, 2021 at 11:22 AM <Eugen.Hristev@microchip.com> wrote:
>
> Thanks for the patch but I already posted a fix some weeks ago :
>
> https://lore.kernel.org/linux-arm-kernel/20210705125708.121902-1-eugen.hristev@microchip.com/
Ok, good. Is that going to make it into v5.14?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: Eugen Hristev <Eugen.Hristev@microchip.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Arnd Bergmann <arnd@arndb.de>,
tomi.valkeinen@ideasonboard.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ludovic Desroches <Ludovic.Desroches@microchip.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] media: atmel: atmel-isc: fix build failures after split
Date: Thu, 22 Jul 2021 13:45:22 +0200 [thread overview]
Message-ID: <CAK8P3a0xp9BxwSt9+WTngsb1K12NGkroBwEf9p5Wg0Knf5umNQ@mail.gmail.com> (raw)
In-Reply-To: <BN9PR11MB5514AA62DD0F2A65828E62D6E8E49@BN9PR11MB5514.namprd11.prod.outlook.com>
On Thu, Jul 22, 2021 at 11:22 AM <Eugen.Hristev@microchip.com> wrote:
>
> Thanks for the patch but I already posted a fix some weeks ago :
>
> https://lore.kernel.org/linux-arm-kernel/20210705125708.121902-1-eugen.hristev@microchip.com/
Ok, good. Is that going to make it into v5.14?
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-22 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 9:04 [PATCH] media: atmel: atmel-isc: fix build failures after split Arnd Bergmann
2021-07-22 9:04 ` Arnd Bergmann
[not found] ` <BN9PR11MB5514AA62DD0F2A65828E62D6E8E49@BN9PR11MB5514.namprd11.prod.outlook.com>
2021-07-22 11:45 ` Arnd Bergmann [this message]
2021-07-22 11:45 ` Arnd Bergmann
2021-07-26 7:02 ` Eugen.Hristev
2021-07-26 7:02 ` Eugen.Hristev
2021-07-29 9:02 ` Hans Verkuil
2021-07-29 9:02 ` Hans Verkuil
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=CAK8P3a0xp9BxwSt9+WTngsb1K12NGkroBwEf9p5Wg0Knf5umNQ@mail.gmail.com \
--to=arnd@kernel.org \
--cc=Eugen.Hristev@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=tomi.valkeinen@ideasonboard.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.