All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org
Subject: Re: [RFC PATCH linux-next] rds: rds_message_zcopy_from_user() can be static
Date: Thu, 8 Mar 2018 06:25:52 -0500	[thread overview]
Message-ID: <20180308112552.GA7919@oracle.com> (raw)
In-Reply-To: <20180308105614.GA22202@cairo>

On (03/08/18 18:56), kbuild test robot wrote:
> 
> Fixes: d40a126b16ea ("rds: refactor zcopy code into rds_message_zcopy_from_user")
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>

Acked-by: Sowmini Varadhan <sowmini.varadhan@oracle.com>

(do I need to separately submit a non-RFC patch for this?)

  reply	other threads:[~2018-03-08 11:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 10:56 [linux-next:master 6181/6533] net/rds/message.c:336:5: sparse: symbol 'rds_message_zcopy_from_user' was not declared. Should it be static? kbuild test robot
2018-03-08 10:56 ` [RFC PATCH linux-next] rds: rds_message_zcopy_from_user() can be static kbuild test robot
2018-03-08 11:25   ` Sowmini Varadhan [this message]
2018-03-09  2:52     ` David Miller

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=20180308112552.GA7919@oracle.com \
    --to=sowmini.varadhan@oracle.com \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=netdev@vger.kernel.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.