From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/f2fs-tools: fix build without blkid
Date: Sun, 22 Sep 2019 21:37:13 +0300 [thread overview]
Message-ID: <87v9tknpnq.fsf@tarshish> (raw)
In-Reply-To: <CAPi7W82y_vepwQe8KrEKu=unRUeEhnhY5VKOriv_uaDTRRnqMQ@mail.gmail.com>
Hi Fabrice,
On Sun, Sep 22 2019, Fabrice Fontaine wrote:
> Le dim. 22 sept. 2019 ? 20:17, Arnout Vandecappelle <arnout@mind.be> a ?crit :
>>
>> On 22/09/2019 10:35, Fabrice Fontaine wrote:
>> > Fixes:
>> > - http://autobuild.buildroot.org/results/c126cb419709367479578b6f118ac9f0d6622689
>> >
>> > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
>>
>> Applied to master, thanks.
>>
>> I assume you sent the patch upstream?
> Nope, I didn't find where to sent it.
Last year I sent a patch to the addresses listed in the F2FS entry of
the kernel's MAINTAINERS:
To: Jaegeuk Kim <jaegeuk@kernel.org>,
Chao Yu <yuchao0@huawei.com>
Cc: linux-f2fs-devel at lists.sourceforge.net
It was accepted as:
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/commit/?id=eefe225a566be9a4d9a176672c40df6585267d5f
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
prev parent reply other threads:[~2019-09-22 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 8:35 [Buildroot] [PATCH 1/1] package/f2fs-tools: fix build without blkid Fabrice Fontaine
2019-09-22 18:17 ` Arnout Vandecappelle
2019-09-22 18:28 ` Fabrice Fontaine
2019-09-22 18:37 ` Baruch Siach [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=87v9tknpnq.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.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 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.