linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Trond Myklebust <trondmy@gmail.com>,
	"open list:NFS, SUNRPC, AND..." <linux-nfs@vger.kernel.org>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH] SUNRPC: Fix TCP receive code on archs with flush_dcache_page()
Date: Thu, 3 Jan 2019 15:00:10 +0100	[thread overview]
Message-ID: <CAMuHMdXTMod81YP5Vtv4KdWVMG3yLO4dR45CO1W4TfDSfg8LmQ@mail.gmail.com> (raw)
In-Reply-To: <20190103135226.7D5F2217F5@mail.kernel.org>

Hi Sasha,

On Thu, Jan 3, 2019 at 2:52 PM Sasha Levin <sashal@kernel.org> wrote:
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 277e4ab7d530 SUNRPC: Simplify TCP receive code by switching to using iterators.
>
> The bot has tested the following trees: v4.20.0,
>
> v4.20.0: Build failed! Errors:
>     net/sunrpc/xprtsock.c:396:24: error: ‘struct bio_vec’ has no member named ‘page’; did you mean ‘bv_page’?
>
>
> How should we proceed with this patch?

Please drop it, as it was superseded by v2.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2019-01-03 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03  0:42 [PATCH] SUNRPC: Fix TCP receive code on archs with flush_dcache_page() Trond Myklebust
2019-01-03  5:29 ` kbuild test robot
2019-01-03  6:45 ` kbuild test robot
2019-01-03 13:52 ` Sasha Levin
2019-01-03 14:00   ` Geert Uytterhoeven [this message]
2019-01-05 20:53     ` Sasha Levin

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=CAMuHMdXTMod81YP5Vtv4KdWVMG3yLO4dR45CO1W4TfDSfg8LmQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=trondmy@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).