linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.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: Sat, 5 Jan 2019 15:53:52 -0500	[thread overview]
Message-ID: <20190105205352.GC166797@sasha-vm> (raw)
In-Reply-To: <CAMuHMdXTMod81YP5Vtv4KdWVMG3yLO4dR45CO1W4TfDSfg8LmQ@mail.gmail.com>

On Thu, Jan 03, 2019 at 03:00:10PM +0100, Geert Uytterhoeven wrote:
>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.

Hi Geert,

These mails don't really mean that the patch got queued anywhere (as
it's obviously not upstream yet). It's more of a heads-up about how this
patch (won't) be backported to various -stable branches.

It's usually easier to get response from people while the patch is still
fresh in their heads rather than a few weeks later :)

--
Thanks,
Sasha

      reply	other threads:[~2019-01-05 20:53 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
2019-01-05 20:53     ` Sasha Levin [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=20190105205352.GC166797@sasha-vm \
    --to=sashal@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-nfs@vger.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).