All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: dsa@cumulusnetworks.com, johannes@sipsolutions.net,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	pablo@netfilter.org, jhs@mojatatu.com, jbenc@redhat.com,
	johannes.berg@intel.com
Subject: Re: [PATCH net-next v5 5/5] netlink: pass extended ACK struct where available
Date: Wed, 12 Apr 2017 11:29:26 -0400 (EDT)	[thread overview]
Message-ID: <20170412.112926.53823287831778729.davem@davemloft.net> (raw)
In-Reply-To: <20170412151531.GL1952@nanopsycho>

From: Jiri Pirko <jiri@resnulli.us>
Date: Wed, 12 Apr 2017 17:15:31 +0200

> Wed, Apr 12, 2017 at 04:55:07PM CEST, dsa@cumulusnetworks.com wrote:
>>On 4/12/17 8:00 AM, Jiri Pirko wrote:
>>> Aside from the tinyfication of desc lines
>>
>>channel your inner Elsa and just let it go
> 
> Not sure why. I still believe it is a mistake so I like to point it out.
> Don't see anything wrong about it :)

I'll just reformat the commit messages when I apply this series if it bothers
you so much Jiri.

I too think that there are more important issues to discuss with this patch
set.

Thanks.

  reply	other threads:[~2017-04-12 15:29 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 12:34 [PATCH net-next v5 0/5] netlink extended ACK reporting Johannes Berg
2017-04-12 12:34 ` [PATCH net-next v5 1/5] netlink: " Johannes Berg
2017-04-12 13:41   ` Jiri Pirko
2017-04-12 13:41     ` Jiri Pirko
2017-04-12 15:06   ` David Ahern
2017-04-12 15:13     ` Jiri Pirko
2017-04-12 15:13       ` Jiri Pirko
2017-04-12 15:28       ` David Miller
2017-04-12 15:21     ` Johannes Berg
2017-04-12 15:30       ` David Miller
2017-04-12 15:30         ` David Miller
2017-04-12 15:32   ` David Ahern
2017-04-12 15:32     ` David Ahern
2017-04-12 12:34 ` [PATCH net-next v5 2/5] genetlink: pass extended ACK report down Johannes Berg
2017-04-12 14:01   ` Jiri Pirko
2017-04-12 12:34 ` [PATCH net-next v5 3/5] netlink: allow sending extended ACK with cookie on success Johannes Berg
2017-04-12 13:47   ` Jiri Pirko
2017-04-12 13:47     ` Jiri Pirko
2017-04-12 13:54     ` Johannes Berg
2017-04-12 12:34 ` [PATCH net-next v5 4/5] netlink: pass extended ACK struct to parsing functions Johannes Berg
2017-04-12 12:34   ` Johannes Berg
2017-04-12 13:17   ` Jiri Pirko
2017-04-12 13:20     ` Johannes Berg
2017-04-12 13:20       ` Johannes Berg
2017-04-12 13:24       ` Jiri Pirko
2017-04-12 14:02     ` Kalle Valo
2017-04-12 14:08       ` Jiri Pirko
2017-04-12 13:56   ` Jiri Pirko
2017-04-12 13:56     ` Jiri Pirko
2017-04-12 12:34 ` [PATCH net-next v5 5/5] netlink: pass extended ACK struct where available Johannes Berg
2017-04-12 12:34   ` Johannes Berg
2017-04-12 14:00   ` Jiri Pirko
2017-04-12 14:55     ` David Ahern
2017-04-12 14:55       ` David Ahern
2017-04-12 15:15       ` Jiri Pirko
2017-04-12 15:29         ` David Miller [this message]
2017-04-12 14:57 ` [PATCH net-next v5 0/5] netlink extended ACK reporting David Ahern

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=20170412.112926.53823287831778729.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dsa@cumulusnetworks.com \
    --cc=jbenc@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.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 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.