From: Jeff Garzik <jeff@garzik.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] final PCI patches for 2.6.26
Date: Thu, 12 Jun 2008 17:45:09 -0400 [thread overview]
Message-ID: <485198E5.80109@garzik.org> (raw)
In-Reply-To: <200806121334.01562.jbarnes@virtuousgeek.org>
Jesse Barnes wrote:
> Some of these may not have seen review on linux-pci, so I'm sending them out
> for comment before I send Linus the pull request.
>
> Any comments/objections?
>
> The biggest patch by far is the resource_wc stuff; it should have been pushed
> earlier, but for some reason I thought Ingo & co. were going to do that...
>
> Thanks,
> Jesse
>
> commit a123c3d9643464c56417680536ed9515f15cffa1
> Author: Yinghai Lu <Yinghai.Lu@Sun.COM>
> Date: Mon May 12 21:21:05 2008 +0200
Although I quite appreciate the addition of patches, IMO it would be
easier to read if the patch descriptions and patches were not mixed
together.
Most 'git pull' things I've seen include a changeset summary (shortlog)
and cumulative patch, when its a single email. Sometimes (i.e. GregKH
and a few others) the individual patches are posted in separate emails.
Either way, it saves one from having to wade through a long email, just
to get an idea of the sum total of the changes...
Regards,
Jeff
next prev parent reply other threads:[~2008-06-12 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 20:34 Jesse Barnes
2008-06-12 21:45 ` Jeff Garzik [this message]
2008-06-12 22:19 ` Jesse Barnes
2008-06-14 22:15 ` Ingo Oeser
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=485198E5.80109@garzik.org \
--to=jeff@garzik.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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
all inboxes | Powered by JetHome®