From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
kbuild test robot <lkp@intel.com>,
kbuild-all@01.org
Subject: Re: [RFC PATCH f2fs] f2fs: f2fs_submit_ipu_bio() can be static
Date: Thu, 14 Mar 2019 10:48:29 -0700 [thread overview]
Message-ID: <20190314174829.GA65912@jaegeuk-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <80739307-8abf-4530-7228-ae737c6eeded@kernel.org>
On 03/14, Chao Yu wrote:
> Hi Jaegeuk,
>
> Could you merge this into ("f2fs: add bio cache for IPU")?
Done.
>
> Thanks,
>
> On 2019-3-14 7:53, kbuild test robot wrote:
> >
> > Fixes: 60686faa1e20 ("f2fs: add bio cache for IPU")
> > Signed-off-by: kbuild test robot <lkp@intel.com>
> > ---
> > data.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> > index 6908469..9381f76 100644
> > --- a/fs/f2fs/data.c
> > +++ b/fs/f2fs/data.c
> > @@ -517,7 +517,7 @@ int f2fs_merge_page_bio(struct f2fs_io_info *fio)
> > return 0;
> > }
> >
> > -void f2fs_submit_ipu_bio(struct f2fs_sb_info *sbi, struct bio **bio,
> > +static void f2fs_submit_ipu_bio(struct f2fs_sb_info *sbi, struct bio **bio,
> > struct page *page)
> > {
> > if (!bio)
> >
prev parent reply other threads:[~2019-03-14 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 23:53 [f2fs:dev-test 54/55] fs/f2fs/data.c:520:6: sparse: symbol 'f2fs_submit_ipu_bio' was not declared. Should it be static? kbuild test robot
2019-03-13 23:53 ` [RFC PATCH f2fs] f2fs: f2fs_submit_ipu_bio() can be static kbuild test robot
2019-03-14 14:35 ` Chao Yu
2019-03-14 17:48 ` Jaegeuk Kim [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=20190314174829.GA65912@jaegeuk-macbookpro.roam.corp.google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=lkp@intel.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 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.