netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathaniel Yazdani <n1ght.4nd.d4y@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
	kaber@trash.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IPv6: simplify & condense a few declarations & statements
Date: Wed, 17 Apr 2013 11:02:48 -0700	[thread overview]
Message-ID: <1366221768.1839.2.camel@lizardlounge> (raw)
In-Reply-To: <20130417.132818.1433580618679802344.davem@davemloft.net>

>I'm not applying this even with the long lines in the commit message
>fixes, sorry.

Okay, well thank you for your time nonetheless.

      reply	other threads:[~2013-04-17 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 17:20 [PATCH] IPv6: simplify & condense a few declarations & statements Nathaniel Yazdani
2013-04-17 17:28 ` David Miller
2013-04-17 18:02   ` Nathaniel Yazdani [this message]

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=1366221768.1839.2.camel@lizardlounge \
    --to=n1ght.4nd.d4y@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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).