From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: fix name of config variable
Date: Mon, 5 Jun 2017 18:42:40 +0200 [thread overview]
Message-ID: <20170605164240.GC3944@scaer> (raw)
In-Reply-To: <20170605115409.5e7c55d8@free-electrons.com>
Thomas, All,
On 2017-06-05 11:54 +0200, Thomas Petazzoni spake thusly:
> On Sun, 4 Jun 2017 11:48:39 +0200, Yann E. MORIN wrote:
> > In 4c10eedc1 (systemd: enable required kernel features), we added
> > setting a few required kernel features to ensure systemd works.
> >
> > However, there was a typo for one of the variables: CONFIG_TMPFS_XATTR
> > was written as CONFIG_TMPFS_POSIX_XATTR, which does not exist (and never
> > ever existed, at least not since 2.6.12)...
> >
> > Fixes #9926.
>
> The patch looks good, but I'm not sure why you say it fixes #9926. It
> has been noticed as part of the #9926 discussion, but to me it doesn't
> fix this bug.
>
> Could you clarify?
OK, I mis-read the comment in #9926. I does not fix it.
Still, the patch is meaningful on its own.
Can you just drop the "Fixes #9926" part before applying, please? ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-06-05 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 9:48 [Buildroot] [PATCH] linux: fix name of config variable Yann E. MORIN
2017-06-05 9:54 ` Thomas Petazzoni
2017-06-05 16:42 ` Yann E. MORIN [this message]
2017-06-08 14:51 ` Peter Korsgaard
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=20170605164240.GC3944@scaer \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox