linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>
Cc: Rolf Eike Beer <eb@emlix.com>
Subject: Re: [f2fs-dev] [PATCH 4/4] lib: pass all needed include paths to libf2fs
Date: Thu, 18 Jun 2020 11:33:32 +0800	[thread overview]
Message-ID: <f36b3a03-876c-d699-0ccb-7a10d01bf76d@huawei.com> (raw)
In-Reply-To: <20200615180843.153299-4-jaegeuk@kernel.org>

On 2020/6/16 2:08, Jaegeuk Kim wrote:
> From: Rolf Eike Beer <eb@emlix.com>
> 
> Otherwise the paths to uuid and blkid headers extracted from pkg-config are not
> respected.
> 
> Signed-off-by: Rolf Eike Beer <eb@emlix.com>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2020-06-18  3:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 18:08 [f2fs-dev] [PATCH 1/4] lib: fix include path for uuid.h Jaegeuk Kim
2020-06-15 18:08 ` [f2fs-dev] [PATCH 2/4] lib: fix include path for blkid.h Jaegeuk Kim
2020-06-18  3:33   ` Chao Yu
2020-06-15 18:08 ` [f2fs-dev] [PATCH 3/4] lib: use ${libuuid_LIBS} instead of -luuid everywhere Jaegeuk Kim
2020-06-18  3:33   ` Chao Yu
2020-06-15 18:08 ` [f2fs-dev] [PATCH 4/4] lib: pass all needed include paths to libf2fs Jaegeuk Kim
2020-06-18  3:33   ` Chao Yu [this message]
2020-06-18  3:32 ` [f2fs-dev] [PATCH 1/4] lib: fix include path for uuid.h Chao Yu

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=f36b3a03-876c-d699-0ccb-7a10d01bf76d@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=eb@emlix.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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).