From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] network-manager: sync kernel headers comment with actual dependency
Date: Sun, 1 Jul 2018 22:01:22 +0200 [thread overview]
Message-ID: <20180701200121.GB7259@x230> (raw)
In-Reply-To: <20180701110331.50944ca6@windsurf.home>
Hi Thomas,
> Hello,
> On Sun, 1 Jul 2018 00:19:15 +0200, Thomas Petazzoni wrote:
> > In commit 52282828f06dc8aa3f721727f68a5096b9ed8b49
> > ("package/network-manager: add patches to build with kernel headers
> > 3.2"), network-manager was changed to build with kernel headers as old
> > as 3.2, instead of 3.7 before. The dependency was changed accordingly,
> > but the Config.in comment was not.
> > This commit fixes this inconsistency.
thanks for my old error.
Kind regards,
Petr
next prev parent reply other threads:[~2018-07-01 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 22:19 [Buildroot] [PATCH] network-manager: sync kernel headers comment with actual dependency Thomas Petazzoni
2018-07-01 8:54 ` Yann E. MORIN
2018-07-01 9:03 ` Thomas Petazzoni
2018-07-01 20:01 ` Petr Vorel [this message]
2018-07-19 10:09 ` 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=20180701200121.GB7259@x230 \
--to=petr.vorel@gmail.com \
--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