All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
Cc: CIFS <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux-Next Mailing List
	<linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux Kernel Mailing List
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Ronnie Sahlberg
	<lsahlber-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Pavel Shilovsky <pshilov-0li6OtcxBFHby3iVrkZq2A@public.gmane.org>,
	Aurelien Aptel <aaptel-IBi9RG/b67k@public.gmane.org>
Subject: Re: linux-next: build warning after merge of the cifs tree
Date: Mon, 20 Nov 2017 17:37:52 -0600	[thread overview]
Message-ID: <CAH2r5muoR_8eFK+ZNUqdrzWTw3h6T9uHBYD4PbCUKYK6xCn1=A@mail.gmail.com> (raw)
In-Reply-To: <20171121101916.4970d5f9-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>

fix for this warning merged into cifs-2.6.git for-next

On Mon, Nov 20, 2017 at 5:19 PM, Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org> wrote:
> Hi all,
>
> After merging the cifs tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/cifs/smb2pdu.c: In function 'SMB2_read':
> fs/cifs/smb2pdu.c:2677:18: warning: unused variable 'rqst' [-Wunused-variable]
>   struct smb_rqst rqst = { .rq_iov = iov,
>                   ^
>
> Introduced by commit
>
>   889143494e16 ("cifs: remove rfc1002 header from smb2 read/write requests")
>
> --
> Cheers,
> Stephen Rothwell



-- 
Thanks,

Steve

WARNING: multiple messages have this Message-ID (diff)
From: Steve French <smfrench@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: CIFS <linux-cifs@vger.kernel.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ronnie Sahlberg <lsahlber@redhat.com>,
	Pavel Shilovsky <pshilov@microsoft.com>,
	Aurelien Aptel <aaptel@suse.com>
Subject: Re: linux-next: build warning after merge of the cifs tree
Date: Mon, 20 Nov 2017 17:37:52 -0600	[thread overview]
Message-ID: <CAH2r5muoR_8eFK+ZNUqdrzWTw3h6T9uHBYD4PbCUKYK6xCn1=A@mail.gmail.com> (raw)
In-Reply-To: <20171121101916.4970d5f9@canb.auug.org.au>

fix for this warning merged into cifs-2.6.git for-next

On Mon, Nov 20, 2017 at 5:19 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> After merging the cifs tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/cifs/smb2pdu.c: In function 'SMB2_read':
> fs/cifs/smb2pdu.c:2677:18: warning: unused variable 'rqst' [-Wunused-variable]
>   struct smb_rqst rqst = { .rq_iov = iov,
>                   ^
>
> Introduced by commit
>
>   889143494e16 ("cifs: remove rfc1002 header from smb2 read/write requests")
>
> --
> Cheers,
> Stephen Rothwell



-- 
Thanks,

Steve

  parent reply	other threads:[~2017-11-20 23:37 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 23:19 linux-next: build warning after merge of the cifs tree Stephen Rothwell
     [not found] ` <20171121101916.4970d5f9-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2017-11-20 23:37   ` Steve French [this message]
2017-11-20 23:37     ` Steve French
  -- strict thread matches above, loose matches on Subject: below --
2024-01-19  1:47 Stephen Rothwell
2024-01-19  3:02 ` Steve French
2022-05-23  0:57 Stephen Rothwell
2022-05-23  2:29 ` Steve French
2021-02-04 22:51 Stephen Rothwell
2019-07-18 23:16 Stephen Rothwell
2019-07-18 23:38 ` Steve French
2018-01-03 22:33 Stephen Rothwell
2018-01-03 22:44 ` Steve French
     [not found]   ` <CAH2r5mvgtC3Y_aLxk7-_R8E=ohR1LoFSkiqZZ6rhn9azXY05xw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-04  5:52     ` Stephen Rothwell
2018-01-04  5:52       ` Stephen Rothwell
2017-06-26  0:07 Stephen Rothwell
2017-06-26  0:07 ` Stephen Rothwell
     [not found] ` <20170626100728.0494601c-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2017-06-26 16:57   ` Steve French
2017-06-26 16:57     ` Steve French
2011-01-31  2:30 Stephen Rothwell
2011-01-31  2:30 ` Stephen Rothwell
2011-01-31 10:49 ` Suresh Jayaraman
     [not found]   ` <4D4693CF.9090903-l3A5Bk7waGM@public.gmane.org>
2011-01-31 11:38     ` Pavel Shilovsky
2011-01-31 11:38       ` Pavel Shilovsky
2011-01-31 12:29   ` Jeff Layton
2011-01-31  2:27 Stephen Rothwell
2011-01-31  2:27 ` Stephen Rothwell
     [not found] ` <20110131132743.4ae5d4ae.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2011-01-31  3:25   ` Steve French
2011-01-31  3:25     ` Steve French
2011-01-31  2:25 Stephen Rothwell
2011-01-31  2:25 ` Stephen Rothwell
2011-01-31  2:25 ` Stephen Rothwell
2011-01-21  1:05 Stephen Rothwell
2011-01-21  1:05 ` Stephen Rothwell
2011-01-21  1:05 ` Stephen Rothwell
2011-01-21  1:20 ` Jeff Layton
2011-01-21  1:20   ` Jeff Layton
2010-09-24  3:55 Stephen Rothwell
2010-09-24  3:55 ` Stephen Rothwell
     [not found] ` <20100924135531.96e5ac72.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-10-19  5:21   ` Stephen Rothwell
2010-10-19  5:21     ` Stephen Rothwell
2010-10-19  5:21     ` Stephen Rothwell
2010-10-19 13:13     ` Jeff Layton
2010-10-19 13:13       ` Jeff Layton
     [not found]       ` <20101019091339.38e45faa-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-10-19 15:48         ` Shirish Pargaonkar
2010-10-19 15:48           ` Shirish Pargaonkar
2010-09-24  3:48 Stephen Rothwell
2010-09-24  3:48 ` Stephen Rothwell
2010-09-24  3:48 ` Stephen Rothwell
2010-09-24 11:13 ` Jeff Layton
2010-09-24 11:13   ` Jeff Layton
2010-08-26  1:02 Stephen Rothwell
2010-08-26  1:02 ` Stephen Rothwell
2010-08-26  1:02 ` Stephen Rothwell
     [not found] ` <20100826110229.931ab5bf.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-08-26  2:07   ` Steve French
2010-08-26  2:07     ` Steve French
2010-04-01  0:50 Stephen Rothwell
2010-04-01  0:50 ` Stephen Rothwell

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='CAH2r5muoR_8eFK+ZNUqdrzWTw3h6T9uHBYD4PbCUKYK6xCn1=A@mail.gmail.com' \
    --to=smfrench-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=aaptel-IBi9RG/b67k@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lsahlber-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=pshilov-0li6OtcxBFHby3iVrkZq2A@public.gmane.org \
    --cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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.