From: Nathan Chancellor <nathan@kernel.org>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev
Subject: Re: [GIT PULL for v5.17-rc1] New year's media updates
Date: Mon, 3 Jan 2022 11:45:21 -0700 [thread overview]
Message-ID: <YdNEQbgpBJP2lIiP@archlinux-ax161> (raw)
In-Reply-To: <20220101024250.39c9b5b6@coco.lan>
Hi Mauro,
On Sat, Jan 01, 2022 at 02:42:50AM +0100, Mauro Carvalho Chehab wrote:
> media: atomisp: shift some structs from input_system_local
Please consider applying my patch that fixes this one to avoid breaking
certain distribution configurations when CONFIG_WERROR is enabled:
https://lore.kernel.org/r/20211227164243.2329724-1-nathan@kernel.org/
I know there has not been much time between when I sent it and now but
there have been two reports about it from the kernel test robot (one was
back in November) and it is rather noisy in a build.
https://lore.kernel.org/r/202111182229.beNw3l9E-lkp@intel.com/
https://lore.kernel.org/r/202112311809.bEKUPkjh-lkp@intel.com/
If it cannot be applied now because the tag has been created and the
pull has been sent, could you make sure it makes it in a fixes pull
request?
Thank you!
Nathan
next prev parent reply other threads:[~2022-01-03 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 1:42 [GIT PULL for v5.17-rc1] New year's media updates Mauro Carvalho Chehab
2022-01-01 1:47 ` [GIT PULL for v5.17-rc1] New year's media updates (#79714) Jenkins
2022-01-03 18:45 ` Nathan Chancellor [this message]
2022-01-10 15:07 ` [GIT PULL for v5.17-rc1] New year's media updates Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2022-01-01 1:29 Mauro Carvalho Chehab
2022-01-11 3:06 ` pr-tracker-bot
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=YdNEQbgpBJP2lIiP@archlinux-ax161 \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).