From: Maz The Northener <mazziesaccount@gmail.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Matti Vaittinen <matti.vaittinen@nsn.com>,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] IPv6 - support for NLM_F_* flags at IPv6 routing requests
Date: Wed, 2 Nov 2011 08:28:20 +0200 [thread overview]
Message-ID: <CANhJrGMeE7qsNBY6Sd2+tUWOezEv=Grc4uoArqAz=Ru4Me8Dsg@mail.gmail.com> (raw)
In-Reply-To: <20111101224302.6d370068@s6510.linuxnetplumber.net>
On Tue, Nov 1, 2011 at 11:43 PM, Stephen Hemminger
<shemminger@vyatta.com> wrote:
> On Tue, 01 Nov 2011 16:22:27 +0200
> Matti Vaittinen <matti.vaittinen@nsn.com> wrote:
>
>>
>> +#define RT6_CANT_CREATE ((int)-1)
>> #define RT6_DEBUG 2
>
> Rather than introduce a new error flag, why not convert the code
> to use the kernel standard PTR_ERR() macros?
> --
Thanks for comment Stephen, I admitt I felt there was something rotten
in adding a new define. And as to why not use PTR_ERR() - I did not
know about such a facility. I'll fix this to be
return ERR_PTR(-ENOENT);
and at calling function check for
if (PTR_ERR(fn) == -ENOENT)
I guess that is correct way?
And finally couple of questions about sending patches (I'm a new guy
in this "house" of yours):
Is it Ok to add patch as attachment? I'm having difficulties in using
a client which allows sending plain text.
And is it Ok to create patch against linux 3.1-rc4? I've never used
git, and thus obtaining 3.1-rc4 from kernel.org is the easiest way for
me.
--Matti Vaittinen
next prev parent reply other threads:[~2011-11-02 6:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 14:22 [PATCH] IPv6 - support for NLM_F_* flags at IPv6 routing requests Matti Vaittinen
2011-11-01 21:43 ` Stephen Hemminger
2011-11-02 6:28 ` Maz The Northener [this message]
2011-11-02 7:09 ` Matti Vaittinen
2011-11-02 7:28 ` David Miller
2011-11-02 16:21 ` Stephen Hemminger
2011-11-03 6:55 ` Maz The Northener
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='CANhJrGMeE7qsNBY6Sd2+tUWOezEv=Grc4uoArqAz=Ru4Me8Dsg@mail.gmail.com' \
--to=mazziesaccount@gmail.com \
--cc=davem@davemloft.net \
--cc=matti.vaittinen@nsn.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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).