From: Nathan Lynch <ntl@pobox.com>
To: linuxppc-dev@ozlabs.org
Cc: Paul Mackerras <paulus@samba.org>
Subject: [PATCH 01/11] rtas_pci_ops: use named structure member initializers
Date: Thu, 9 Aug 2007 14:18:36 -0500 [thread overview]
Message-ID: <11866871293663-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/kernel/rtas_pci.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/kernel/rtas_pci.c b/arch/powerpc/kernel/rtas_pci.c
index a5de621..21f14e5 100644
--- a/arch/powerpc/kernel/rtas_pci.c
+++ b/arch/powerpc/kernel/rtas_pci.c
@@ -171,8 +171,8 @@ static int rtas_pci_write_config(struct pci_bus *bus,
}
struct pci_ops rtas_pci_ops = {
- rtas_pci_read_config,
- rtas_pci_write_config
+ .read = rtas_pci_read_config,
+ .write = rtas_pci_write_config,
};
int is_python(struct device_node *dev)
--
1.5.2.4
next prev parent reply other threads:[~2007-08-09 19:18 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 ` Nathan Lynch [this message]
2007-08-09 19:18 ` [PATCH 02/11] celleb_fake_pci_ops: use named structure member initializers 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 ` [PATCH 11/11] tsi108_direct_pci_ops: " Nathan Lynch
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=11866871293663-git-send-email-ntl@pobox.com \
--to=ntl@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.