From: Andrew Lunn <andrew@lunn.ch>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: netdev@vger.kernel.org, linville@redhat.com
Subject: Re: [PATCH v2 1/2] ethtool: sync ethtool-copy.h with linux-next from 30/05/2019
Date: Fri, 31 May 2019 18:04:15 +0200 [thread overview]
Message-ID: <20190531160415.GC23821@lunn.ch> (raw)
In-Reply-To: <20190531155355.GG15954@unicorn.suse.cz>
> Reviewed-by: Michal Kubecek <mkubecek@suse.cz>
>
> BtW, this differs from the file "make headers_install" produces in
> net-next but only in white space so that it doesn't really matter and it
> gets sorted in a future sync.
Yes, there is something odd going on. It looks like two tabs have been
converted to spaces in the ethtool copy. I left them alone, since i
did not add them.
Andrew
next prev parent reply other threads:[~2019-05-31 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 13:57 [PATCH v2 0/2] Add 100BaseT1 and 1000BaseT1 Andrew Lunn
2019-05-31 13:57 ` [PATCH v2 1/2] ethtool: sync ethtool-copy.h with linux-next from 30/05/2019 Andrew Lunn
2019-05-31 15:53 ` Michal Kubecek
2019-05-31 16:04 ` Andrew Lunn [this message]
2019-05-31 13:57 ` [PATCH v2 2/2] ethtool: Add 100BaseT1 and 1000BaseT1 link modes Andrew Lunn
2019-05-31 15:50 ` Michal Kubecek
2019-06-14 18:40 ` [PATCH v2 0/2] Add 100BaseT1 and 1000BaseT1 John W. Linville
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=20190531160415.GC23821@lunn.ch \
--to=andrew@lunn.ch \
--cc=linville@redhat.com \
--cc=mkubecek@suse.cz \
--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).