From: "John W. Linville" <linville@tuxdriver.com>
To: Scott Branden <scott.branden@broadcom.com>
Cc: "Greenwalt, Paul" <paul.greenwalt@intel.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: ethtool-copy.h out of sync with linux header file?
Date: Wed, 6 Dec 2017 09:19:50 -0500 [thread overview]
Message-ID: <20171206141950.GA1271@tuxdriver.com> (raw)
In-Reply-To: <418b362a-6a77-1fd8-9df8-056f55cc8f55@broadcom.com>
On Tue, Dec 05, 2017 at 12:25:51PM -0800, Scott Branden wrote:
> Hi Paul,
>
>
> On 17-12-04 01:00 PM, Greenwalt, Paul wrote:
> > John,
> >
> > Can this patch be reverted? As Stephen Hemminger mentioned
> > there is an ABI compatibility issue with this patch:
> I can add the revert into a patch series followed by the sync of
> ethtool-copy.h with net-netx ethtool.h
Yes, exactly. I see that you did just that in your later series
submission.
Thanks!
John
> >
> > https://patchwork.ozlabs.org/patch/806049/#1757846
> >
> > Thanks,
> > Paul
> >
> > > -----Original Message-----
> > > From: Scott Branden [mailto:scott.branden@broadcom.com]
> > > Sent: Monday, December 4, 2017 12:07 PM
> > > To: linville@tuxdriver.com; Greenwalt, Paul <paul.greenwalt@intel.com>
> > > Cc: netdev <netdev@vger.kernel.org>
> > > Subject: ethtool-copy.h out of sync with linux header file?
> > >
> > > Hi Paul/John,
> > >
> > > I see a commit "ethtool: Add DMA Coalescing support" was added to
> > > ethtool-copy.h yet I cannot find the change in the ethtool.h in the
> > > linux kernel.
> > >
> > > As such, I am unable to commit a change to ethtool-copy.h to sync it
> > > with net-next. If I sync then ethtool will fail to compile.
> > >
> > > Please advise.
> > >
> > > Thanks,
> > >
> > > Scott
> > >
> > >
>
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2017-12-06 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 20:07 ethtool-copy.h out of sync with linux header file? Scott Branden
2017-12-04 21:00 ` Greenwalt, Paul
2017-12-05 20:25 ` Scott Branden
2017-12-06 14:19 ` John W. Linville [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=20171206141950.GA1271@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=paul.greenwalt@intel.com \
--cc=scott.branden@broadcom.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).