From: Dan Carpenter <dan.carpenter@oracle.com>
To: Peter Huewe <peterhuewe@gmx.de>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: [PATCH v2] staging/xgifb: Convert pci_table entries to PCI_DEVICE (if PCI_ANY_ID is used)
Date: Mon, 7 Nov 2011 01:39:15 +0300 [thread overview]
Message-ID: <20111106223915.GT4682@mwanda> (raw)
In-Reply-To: <1320617548-9506-1-git-send-email-peterhuewe@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On Sun, Nov 06, 2011 at 11:12:28PM +0100, Peter Huewe wrote:
> This patch converts pci_table entries to use the PCI_DEVICE macro,
> if .subvendor and .subdevice are set to PCI_ANY_ID,
> and thus improves readability.
>
> v2:
> Since the driver_data field isn't used anywhere we can also drop the
> assignments for class, class_mask and driver_data.
> (found by Aaro Koskinen)
>
> KernelVersion: Staging-20111106
Don't put that into the permanent changelog.
Sometimes we ask people what tree they wrote a patch against, but the
truth is that we don't actually care.
Q: Your patch doesn't apply. Which tree did you do it against?
A: Blah blah blah long explanation.
Q: Oh that's very nice and lovely. Please redo it against today's
-next tree.
For bug fixes where it could go into either the current kernel or the
next, then it is nice to say. Normally people want a [patch -next
v2] in the subject which will get removed by git am. Or below the
--- dashes.
regards,
dan carpenter
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-11-06 22:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 21:05 [PATCH] staging/xgifb: Convert pci_table entries to PCI_DEVICE (if PCI_ANY_ID is used) Peter Huewe
2011-11-06 21:37 ` Aaro Koskinen
2011-11-06 22:02 ` Peter Hüwe
2011-11-06 22:12 ` [PATCH v2] " Peter Huewe
2011-11-06 22:39 ` Dan Carpenter [this message]
2011-11-06 22:45 ` [PATCH v3] " Peter Huewe
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=20111106223915.GT4682@mwanda \
--to=dan.carpenter@oracle.com \
--cc=aaro.koskinen@iki.fi \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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