From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] MFD for v4.4
Date: Mon, 9 Nov 2015 19:01:13 +0530 [thread overview]
Message-ID: <20151109133113.GA9327@sudip-pc> (raw)
In-Reply-To: <20151107124230.GF3378@x1>
On Sat, Nov 07, 2015 at 12:42:30PM +0000, Lee Jones wrote:
> On Fri, 06 Nov 2015, Linus Torvalds wrote:
>
> > On Fri, Nov 6, 2015 at 12:04 AM, Lee Jones <lee.jones@linaro.org> wrote:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/mfd-for-linus-4.4
> >
> > Ugh.
> >
> > Maintainers, *please* check new warnings you introduce. We don't have
> > that many compiler warnings in the kernel, you shouldn't be
> > introducing new ones and not notice.
> >
> > This pull request introduces this silly new warning:
> >
> > drivers/mfd/rtsx_pcr.c: In function ‘rtsx_pci_set_pull_ctl’:
> > drivers/mfd/rtsx_pcr.c:565:6: warning: unused variable ‘err’
> > [-Wunused-variable]
> > int err;
> > ^
> >
> > due to commit b158b69a3765 ("mfd: rtsx: Simplify function return
> > logic") that removes the actual use of the variable, but not the
> > variable itself.
>
> I thought these were cleaned up. Apologies for that.
Yes, Fix was submitted. https://lkml.org/lkml/2015/10/7/301
I even got your applied message. (https://lkml.org/lkml/2015/10/13/149)
regards
sudip
next prev parent reply other threads:[~2015-11-09 13:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 8:04 [GIT PULL] MFD for v4.4 Lee Jones
2015-11-06 18:37 ` Linus Torvalds
2015-11-06 21:19 ` Mark Brown
2015-11-06 18:46 ` Linus Torvalds
2015-11-07 12:42 ` Lee Jones
2015-11-07 19:29 ` Linus Torvalds
2015-11-09 13:31 ` Sudip Mukherjee [this message]
2015-11-10 9:38 ` Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2016-01-14 9:19 Lee Jones
2016-01-14 14:11 ` Stephen Rothwell
2016-01-14 15:32 ` Lee Jones
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=20151109133113.GA9327@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@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.