All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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>
Subject: Re: [GIT PULL for v5.8-rc1] media updates
Date: Thu, 4 Jun 2020 08:20:52 +0200	[thread overview]
Message-ID: <20200604082052.298d534f@coco.lan> (raw)
In-Reply-To: <CAHk-=wg0=J7VXoEL0eCNmguyj-z7G-iByHcUV02nrmw10GCZ3A@mail.gmail.com>

Em Wed, 3 Jun 2020 21:21:06 -0700
Linus Torvalds <torvalds@linux-foundation.org> escreveu:

> On Wed, Jun 3, 2020 at 1:06 AM Mauro Carvalho Chehab
> <mchehab+huawei@kernel.org> wrote:
> >
> >   - The atomisp staging driver was resurrected. It is meant to work with
> >     4 generations of cameras on Atom-based laptops, tablets and cell
> >     phones. So, it seems worth investing time to cleanup this driver and
> >     making it in good shape.  
> 
> Hmm. It causes a warning for me:
> 
>    drivers/staging/media/atomisp/pci/atomisp_v4l2.c:764:12: warning:
> ‘atomisp_mrfld_power’ defined but not used [-Wunused-function]
> 
> which is a bit annoying.
> 
> I can see the FIXME's there, but the warning still isn't acceptable.
> 
> I'll add a fixup commit. I was going to do it in the merge itself, but
> decided that was a bit too subtle.

OK!

I have a patch like that already on a separate pile of patches,
which address several other things. I opted to place them in
separate, in order to give people some time to comment and review.

My plan is to keep them on linux-next and submit you next week, if
ok for you.

The new series should drop all LLVM warnings and add SPDX headers,
among other things. 

Thanks,
Mauro

  reply	other threads:[~2020-06-04  6:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03  8:05 [GIT PULL for v5.8-rc1] media updates Mauro Carvalho Chehab
2020-06-04  4:13 ` Linus Torvalds
2020-06-04  6:13   ` Mauro Carvalho Chehab
2020-06-04  4:21 ` Linus Torvalds
2020-06-04  6:20   ` Mauro Carvalho Chehab [this message]
2020-06-04  4:35 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2020-06-12 23:26 Mauro Carvalho Chehab
2020-06-13 20:25 ` 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=20200604082052.298d534f@coco.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.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 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.