From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
airlied@redhat.com, thomas@shipmail.org
Subject: Re: [PATCH] bugfix and cleanup patches in the TTM code for 3.1.
Date: Wed, 8 Jun 2011 10:33:08 -0700 [thread overview]
Message-ID: <20110608103308.483c41fe.randy.dunlap@oracle.com> (raw)
In-Reply-To: <BANLkTikrO=skNyEcRsA7FKE+TGVwz7pXzQ@mail.gmail.com>
On Wed, 8 Jun 2011 19:30:22 +0200 Rafał Miłecki wrote:
> Hi Konrad,
>
> 2011/6/8 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>:
> > The bug-fix "ttm: Do not increment the amount of pages in a pool by the current amount"
> > I never observed, but found while looking at the code. The cleanup patch:
> > "ttm: Fix spelling mistakes and remove unused #ifdef", I had posted earlier and Randy
> > Dunlap graciously added some extra cleanups - which I have rolled in.
>
> This is safe to put comments to the patch in the following place:
>
>
> Signed-off-by: (...)
> ---
> RIGHT HERE
> ---
> drivers/(...)
>
>
> When applying such a patch comments will not be visible in git log.
> You may find this easier method of commenting your patches.
Yes, it would remove the temptation to make a patch 0/<small_number>
that several people are (sadly) using recently.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-06-08 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 17:06 [PATCH] bugfix and cleanup patches in the TTM code for 3.1 Konrad Rzeszutek Wilk
2011-06-08 17:06 ` [PATCH] ttm: Do not increment the amount of pages in a pool by the current amount Konrad Rzeszutek Wilk
2011-06-08 17:06 ` [PATCH] ttm: Fix spelling mistakes and remove unused #ifdef Konrad Rzeszutek Wilk
2011-06-08 17:30 ` [PATCH] bugfix and cleanup patches in the TTM code for 3.1 Rafał Miłecki
2011-06-08 17:33 ` Randy Dunlap [this message]
2011-06-08 18:20 ` Konrad Rzeszutek Wilk
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=20110608103308.483c41fe.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@shipmail.org \
--cc=zajec5@gmail.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