From: Nathan Lynch <ntl@pobox.com>
To: linuxppc-dev@ozlabs.org
Cc: Alexandre Bounine <alexandreb@tundra.com>,
Paul Mackerras <paulus@samba.org>
Subject: [PATCH 11/11] tsi108_direct_pci_ops: use named structure member initializers
Date: Thu, 9 Aug 2007 14:18:46 -0500 [thread overview]
Message-ID: <1186687168786-git-send-email-ntl@pobox.com> (raw)
In-Reply-To: <11866871262306-git-send-email-ntl@pobox.com>
Signed-off-by: Nathan Lynch <ntl@pobox.com>
---
arch/powerpc/sysdev/tsi108_pci.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/sysdev/tsi108_pci.c b/arch/powerpc/sysdev/tsi108_pci.c
index 90db8a7..cf0bfbd 100644
--- a/arch/powerpc/sysdev/tsi108_pci.c
+++ b/arch/powerpc/sysdev/tsi108_pci.c
@@ -193,8 +193,8 @@ void tsi108_clear_pci_cfg_error(void)
}
static struct pci_ops tsi108_direct_pci_ops = {
- tsi108_direct_read_config,
- tsi108_direct_write_config
+ .read = tsi108_direct_read_config,
+ .write = tsi108_direct_write_config,
};
int __init tsi108_setup_pci(struct device_node *dev, u32 cfg_phys, int primary)
--
1.5.2.4
prev parent reply other threads:[~2007-08-09 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 19:18 [trivial] use named structure member initializers for pci_ops structures Nathan Lynch
2007-08-09 19:18 ` [PATCH 01/11] rtas_pci_ops: use named structure member initializers Nathan Lynch
2007-08-09 19:18 ` [PATCH 02/11] celleb_fake_pci_ops: " Nathan Lynch
2007-08-09 19:18 ` [PATCH 03/11] celleb_epci_ops: " Nathan Lynch
2007-08-09 19:18 ` [PATCH 04/11] maple pci_ops: " Nathan Lynch
2007-08-09 19:18 ` [PATCH 05/11] pa_pxp_ops: " Nathan Lynch
2007-08-09 19:57 ` Olof Johansson
2007-08-09 19:18 ` [PATCH 06/11] powermac pci_ops: " Nathan Lynch
2007-08-09 19:18 ` [PATCH 07/11] null_pci_ops: " Nathan Lynch
2007-08-09 19:18 ` [PATCH 08/11] efika rtas_pci_ops: " Nathan Lynch
2007-08-09 19:18 ` [PATCH 09/11] chrp pci_ops: " Nathan Lynch
2007-08-09 19:18 ` [PATCH 10/11] indirect_pci_ops: " Nathan Lynch
2007-08-09 19:18 ` Nathan Lynch [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=1186687168786-git-send-email-ntl@pobox.com \
--to=ntl@pobox.com \
--cc=alexandreb@tundra.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).