linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Jan-Bernd Themann <ossthema@de.ibm.com>
Cc: Thomas Klein <tklein@de.ibm.com>,
	Jan-Bernd Themann <themann@de.ibm.com>,
	pmac@au1.ibm.com, linux-kernel <linux-kernel@vger.kernel.org>,
	linux-ppc <linuxppc-dev@ozlabs.org>,
	Christoph Raisch <raisch@de.ibm.com>,
	Marcus Eder <meder@de.ibm.com>
Subject: Re: [PATCH 2.6.19-rc1] ehea firmware interface based on Anton Blanchard's new hvcall interface
Date: Wed, 27 Sep 2006 17:52:29 -0400	[thread overview]
Message-ID: <451AF29D.2030102@garzik.org> (raw)
In-Reply-To: <200609271847.34258.ossthema@de.ibm.com>

Jan-Bernd Themann wrote:
> Hi Jeff, 
> 
> the last patch did not work, so here is the new patch. The patch is build against
> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev.2.6.git HEAD today.
> Could you give it a try?

Per the standard patch format in Documentation/SubmittingPatches, these 
sort of comments should go beneath the "---" separator.  Otherwise, if 
they are not hand-edited out, they will go into the final changeset 
description.


> This eHEA patch reflects changes according to Anton's new hvcall interface
> which has been commited in Paul's git tree:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git

When is this going upstream?  I don't want things to get too out-of-sync.


> In addition to the above changes the patch includes a bug fix (port state
> notification) and minor changes (default queue length, coding style updates).

These changes should be in a separate patch.  Makes 'git bisect' work 
better, makes the changes more reviewable, and in general follows the 
"separate logical changes" rule.


> diff -Nurp netdev-2.6/drivers/net/ehea/ehea_ethtool.c netdev-2.6_patched/drivers/net/ehea/ehea_ethtool.c
> --- netdev-2.6/drivers/net/ehea/ehea_ethtool.c	2006-09-26 10:27:38.000000000 +0200
> +++ netdev-2.6_patched/drivers/net/ehea/ehea_ethtool.c	2006-09-26 19:28:22.000000000 +0200
> @@ -270,7 +270,7 @@ static void ehea_get_ethtool_stats(struc
>  	kfree(cb6);
>  }
>  
> -const struct ethtool_ops ehea_ethtool_ops = {
> +struct ethtool_ops ehea_ethtool_ops = {
>  	.get_settings = ehea_get_settings,
>  	.get_drvinfo = ehea_get_drvinfo,
>  	.get_msglevel = ehea_get_msglevel,


This is an obvious regression.

	Jeff

  reply	other threads:[~2006-09-27 21:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27 16:47 [PATCH 2.6.19-rc1] ehea firmware interface based on Anton Blanchard's new hvcall interface Jan-Bernd Themann
2006-09-27 21:52 ` Jeff Garzik [this message]
2006-09-27 22:23   ` Paul Mackerras
2006-09-27 22:30     ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2006-09-25 13:50 Jan-Bernd Themann
2006-09-26  0:07 ` Jeff Garzik
2006-09-26  2:53   ` Benjamin Herrenschmidt

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=451AF29D.2030102@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=meder@de.ibm.com \
    --cc=ossthema@de.ibm.com \
    --cc=pmac@au1.ibm.com \
    --cc=raisch@de.ibm.com \
    --cc=themann@de.ibm.com \
    --cc=tklein@de.ibm.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).