mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: PATCH: pata_oldpiix rev 0.2
Date: Tue, 17 Jan 2006 13:40:24 -0800	[thread overview]
Message-ID: <7vpsmq7ctz.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <43CCEF25.2090902@pobox.com> (Jeff Garzik's message of "Tue, 17 Jan 2006 08:20:37 -0500")

Jeff Garzik <jgarzik@pobox.com> writes:

> Alan Cox wrote:
>> static void oldpiix_pata_phy_reset(struct ata_port *ap)
>...
>> static void oldpiix_set_piomode (struct ata_port *ap, struct
>>...
>> 	unsigned int pio	= adev->pio_mode - XFER_PIO_0;
>> 	struct pci_dev *dev	= to_pci_dev(ap->host_set->dev);
>> 	unsigned int idetm_port= ap->hard_port_no ? 0x42 : 0x40;
>
> space after '='?

I think you meant space before '='.

Did you have to quote the entire patch?  It was quite annoying
to read.

Ideally, "this applies on top of your patch, to address these
issues", would be the easiest to read, but that would require
you to actually apply Alan's patch on your tree, do your
modifications and produce another patch (IOW, it would be more
work on your part).  Just to provide quick comments, if you
trimmed the patch you quoted from Alan's when commenting,
leaving enough material for Alan and others to identify the
pieces you are commenting on, it would have been a lot easier to
read (it would be more work for the contributor, but it is his
patch after all).


      reply	other threads:[~2006-01-17 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 15:19 Alan Cox
2006-01-17 13:20 ` Jeff Garzik
2006-01-17 21:40   ` Junio C Hamano [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=7vpsmq7ctz.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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

Powered by JetHome