From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Add config to nfsd to set number of threads
Date: Fri, 26 Feb 2016 00:30:55 +0100 [thread overview]
Message-ID: <56CF8EAF.407@mind.be> (raw)
In-Reply-To: <56CF66D2.2080804@gmx.de>
On 02/25/16 21:40, Andreas Ehmanns wrote:
> Yann,
> is the patch o.k. for you? Shall I resend it using git?
Yes, please send using git. Patches sent as attachments have an even bigger
chance of being ignored than other patches.
However, I can already say that it should be two separate patches: one changing
"done" to OK/FAIL, and a second one doing the functional changes.
Regards,
Arnout
> Please let me know.
>
> Regards,
> Andreas
>
> Am 12.02.2016 um 10:31 schrieb Andreas Ehmanns:
>> Yann,
>> indeed a killall -9 worked. So I reworked the patch. According to Thomas'
>> recommendation I added the OK/FAIL output as done in the dropbox init script.
>> Please have a look at the attached patch. If it's o.k., I'll resend it using git.
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-25 23:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 19:45 [Buildroot] [PATCH 1/1] Add config to nfsd to set number of threads Andreas Ehmanns
2015-12-17 20:04 ` Yann E. MORIN
2015-12-17 20:14 ` Andreas Ehmanns
2015-12-17 20:25 ` Yann E. MORIN
2015-12-17 20:26 ` Andreas Ehmanns
2016-02-04 8:31 ` Andreas Ehmanns
2016-02-04 20:50 ` Yann E. MORIN
2016-02-12 9:31 ` Andreas Ehmanns
2016-02-25 20:40 ` Andreas Ehmanns
2016-02-25 23:30 ` Arnout Vandecappelle [this message]
2016-04-15 8:37 ` Andreas Ehmanns
2016-04-15 9:00 ` Arnout Vandecappelle
2016-04-15 9:09 ` Andreas Ehmanns
2016-04-15 9:23 ` Arnout Vandecappelle
2015-12-17 20:52 ` Thomas Petazzoni
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=56CF8EAF.407@mind.be \
--to=arnout@mind.be \
--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.