From: Jeff Garzik <jgarzik@pobox.com>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ramkrishna Vepa <Ramkrishna.Vepa@neterion.com>,
Sivakumar Subramani <sivakumar.subramani@neterion.com>,
Sreenivasa Honnur <sreenivasa.honnur@neterion.com>,
Rastapur Santosh <santosh.rastapur@neterion.com>,
Wen Xiong <wenxiong@us.ibm.com>,
linux-pci@atrey.karlin.mff.cuni.cz, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2 v4] s2io: add PCI error recovery support
Date: Tue, 22 May 2007 18:48:26 -0400 [thread overview]
Message-ID: <4653733A.3030204@pobox.com> (raw)
In-Reply-To: <20070522224727.GR5921@austin.ibm.com>
Linas Vepstas wrote:
> On Mon, May 21, 2007 at 06:51:45PM -0400, Jeff Garzik wrote:
>>> The part that confuses me is that I'd gotten a message from Jeff
>>> back in March (well before 2.6.21 came out), saying it was in his
>>> development tree; yet, the patch its not in 2.6.22-rc; Torvalds
>>> hasn't yet pulled from it?
>> It only appeared in my tree on May 14. I tend to drop patches that are
>> repeatedly revised, allowing the dust to settle.
>
> OK, a new patch is coming. I did not want to pester you until after -rc1
> came out, but perhaps that was the wrong strategy.
You should be sending patches as soon as they are available, so that
they do not miss merge window + 1.
Jeff
prev parent reply other threads:[~2007-05-22 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 18:58 [PATCH 1/2 v4] s2io: add PCI error recovery support Linas Vepstas
2007-05-21 19:02 ` [PATCH 2/2]: s2io: minor janitoring Linas Vepstas
2007-05-21 21:48 ` [PATCH 1/2 v4] s2io: add PCI error recovery support Andrew Morton
2007-05-21 22:23 ` Linas Vepstas
2007-05-21 22:49 ` Andrew Morton
2007-05-21 22:51 ` Jeff Garzik
2007-05-22 22:47 ` Linas Vepstas
2007-05-22 22:48 ` Jeff Garzik [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=4653733A.3030204@pobox.com \
--to=jgarzik@pobox.com \
--cc=Ramkrishna.Vepa@neterion.com \
--cc=akpm@linux-foundation.org \
--cc=linas@austin.ibm.com \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=netdev@vger.kernel.org \
--cc=santosh.rastapur@neterion.com \
--cc=sivakumar.subramani@neterion.com \
--cc=sreenivasa.honnur@neterion.com \
--cc=wenxiong@us.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).