From: Jean Sacren <sakiwit@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next] skbuff: create skb_panic() to let caller specify panic
Date: Sun, 10 Feb 2013 16:46:52 -0700 [thread overview]
Message-ID: <20130210234651.GD2496@mail.gmail.com> (raw)
In-Reply-To: <20130210182451.GA1602@minipsycho.orion>
From: Jiri Pirko <jiri@resnulli.us>
Date: Sun, 10 Feb 2013 19:24:51 +0100
>
> How about to leave skb_under_panic() and skb_over_panic() wrapping
> functions there just to wrap "skb_panic(skb, sz, addr, __func__);" call?
>
> Seems nice that to state the name in str...
That's really a good idea. If David drops again, I'll implement it.
Thanks a lot,
--
Jean Sacren
next prev parent reply other threads:[~2013-02-10 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 8:23 [PATCH v2 net-next] skbuff: create skb_panic() to let caller specify panic Jean Sacren
2013-02-10 18:24 ` Jiri Pirko
2013-02-10 23:46 ` Jean Sacren [this message]
2013-02-11 18:52 ` David Miller
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=20130210234651.GD2496@mail.gmail.com \
--to=sakiwit@gmail.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
/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).