From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] target updates for v3.17-rc3
Date: Mon, 8 Sep 2014 19:21:16 +1000 [thread overview]
Message-ID: <20140908192116.095e9703@canb.auug.org.au> (raw)
In-Reply-To: <CA+55aFx6_pbUwuyhYYSu+=eAA+7o0LDu251Bo7T2ZYo9vZc1kg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]
Hi Nicholas,
On Sun, 31 Aug 2014 17:51:07 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> On Sun, Aug 31, 2014 at 11:59 AM, Nicholas A. Bellinger
> <nab@linux-iscsi.org> wrote:
> >
> > Note that these patches where originally intended for -rc1, but missed
> > the merge window. They are mostly iser-target related bug-fixes, along
> > with a few other very minor cleanups.
>
> So this pull request was strictly speaking too late for rc3, but I
> went "what the hell, it's small" and pulled it anyway.
>
> And then I get this:
>
> drivers/target/target_core_transport.c: In function
> ‘transport_dump_vpd_ident_type’:
> drivers/target/target_core_transport.c:956:3: warning: passing
> argument 1 of ‘strlen’ makes pointer from integer without a cast
> [enabled by default]
> len = strlen(len);
> ^
> In file included from include/linux/bitmap.h:8:0,
> from include/linux/cpumask.h:11,
> from ./arch/x86/include/asm/cpumask.h:4,
> from ./arch/x86/include/asm/msr.h:10,
> from ./arch/x86/include/asm/processor.h:20,
> from ./arch/x86/include/asm/archrandom.h:26,
> from include/linux/random.h:81,
> from include/linux/net.h:22,
> from drivers/target/target_core_transport.c:26:
> include/linux/string.h:80:24: note: expected ‘const char *’ but
> argument is of type ‘int’
> extern __kernel_size_t strlen(const char *);
> ^
>
> and I just go "Yeah, that broken crap can wait until 3.18 after all".
>
> So it got unpulled.
>
> That "strlen(len)" should clearly be a "strlen(buf)" in that commit
> 6cfa853ceee4, but equally clearly this pull request was pure and utter
> garbage, and that "cleanup" commit was shit that nobody had ever even
> bothered to compile.
I noticed this in linux-next today as well (in the target-update
tree). Could I have that cleaned up, please?
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-09-08 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 18:59 Nicholas A. Bellinger
2014-09-01 0:51 ` Linus Torvalds
2014-09-08 9:21 ` Stephen Rothwell [this message]
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=20140908192116.095e9703@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®