From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Tejun Heo <tj@kernel•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Tom Yan <tom.ty89@gmail•com>
Subject: Re: linux-next: build warnings after merge of the libata tree
Date: Wed, 27 Jul 2016 16:32:31 +1000 [thread overview]
Message-ID: <20160727163231.51e88384@canb.auug.org.au> (raw)
In-Reply-To: <20160721144459.GA22680@htj.duckdns.org>
Hi Tejun,
On Thu, 21 Jul 2016 10:44:59 -0400 Tejun Heo <tj@kernel•org> wrote:
>
> On Thu, Jul 21, 2016 at 03:26:03PM +1000, Stephen Rothwell wrote:
> > Hi Tejun,
> >
> > After merging the libata tree, today's linux-next build (arm
> > multi_v7_defconfig) produced these warning:
> >
> > drivers/ata/libata-scsi.c: In function 'ata_mselect_caching':
> > drivers/ata/libata-scsi.c:3637:28: warning: suggest parentheses around comparison in operand of '&' [-Wparentheses]
> > if (mpage[i + 2] & 0xfb != buf[i] & 0xfb) {
> > ^
> > drivers/ata/libata-scsi.c: In function 'ata_mselect_control':
> > drivers/ata/libata-scsi.c:3702:28: warning: suggest parentheses around comparison in operand of '&' [-Wparentheses]
> > if (mpage[i + 2] & 0xfb != buf[i] & 0xfb) {
> > ^
> >
> > Introduced by commit
> >
> > 9b7844a8c34a ("libata-scsi: fix read-only bits checking in ata_mselect_*()")
>
> Already reverted the patch. Sorry about that.
This patch is still in the libata tree
(git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git#for-next)
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-07-27 6:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 5:26 linux-next: build warnings after merge of the libata tree Stephen Rothwell
2016-07-21 14:44 ` Tejun Heo
2016-07-27 6:32 ` Stephen Rothwell [this message]
2016-07-27 17:33 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2012-07-02 3:19 Stephen Rothwell
2012-07-02 3:21 ` Lin Ming
2012-07-02 3:54 ` Stephen Rothwell
2012-07-02 4:31 ` Lin Ming
2012-07-02 6:11 ` Jeff Garzik
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=20160727163231.51e88384@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tj@kernel$(echo .)org \
--cc=tom.ty89@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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