From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: <dougthompson@xmission.com>, <mchehab@osg.samsung.com>,
<linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/6] edac, mce_amd_inj: Add README file
Date: Fri, 29 May 2015 13:29:26 -0500 [thread overview]
Message-ID: <5568B006.9090804@amd.com> (raw)
In-Reply-To: <20150529153836.GI31435@pd.tnic>
On 5/29/2015 10:38 AM, Borislav Petkov wrote:
>
> This one needs to be split in two - the second one adding the readme file...
Ack.
>> +static ssize_t
>> +inj_readme_read(struct file *filp, char __user *ubuf,
>> + size_t cnt, loff_t *ppos)
>> +{
>> + return simple_read_from_buffer(ubuf, cnt, ppos,
>> + readme_msg, strlen(readme_msg));
>> +}
>> +
>> +static const struct file_operations readme_fops = {
>> + .read = inj_readme_read,
>> +};
>> +
>> static struct dfs_node {
>> char *name;
>> struct dentry *d;
>> const struct file_operations *fops;
>> + umode_t perm;
>> } dfs_fls[] = {
>> - { .name = "status", .fops = &status_fops },
>> - { .name = "misc", .fops = &misc_fops },
>> - { .name = "addr", .fops = &addr_fops },
>> - { .name = "bank", .fops = &bank_fops },
>> - { .name = "flags", .fops = &flags_fops },
>> - { .name = "cpu", .fops = &extcpu_fops },
>> + { .name = "status", .fops = &status_fops, S_IRUSR | S_IWUSR },
>> + { .name = "misc", .fops = &misc_fops, S_IRUSR | S_IWUSR },
>> + { .name = "addr", .fops = &addr_fops, S_IRUSR | S_IWUSR },
>> + { .name = "bank", .fops = &bank_fops, S_IRUSR | S_IWUSR },
>> + { .name = "flags", .fops = &flags_fops, S_IRUSR | S_IWUSR },
>> + { .name = "cpu", .fops = &extcpu_fops, S_IRUSR | S_IWUSR },
>> + { .name = "README", .fops = &readme_fops, S_IRUSR | S_IRGRP |
>> + S_IROTH },
> ... and the first one adding perm to struct dfs_node.
>
Will do.
Thanks,
-Aravind.
next prev parent reply other threads:[~2015-05-29 18:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 19:03 [PATCH 0/6] Updates to EDAC mce_amd_inj Aravind Gopalakrishnan
2015-05-27 19:03 ` [PATCH 1/6] edac, mce_amd_inj: Use MCE_INJECT_GET for bank Aravind Gopalakrishnan
2015-05-27 19:03 ` [PATCH 2/6] edac, mce_amd_inj: Rework sanity check for inj_bank_set Aravind Gopalakrishnan
2015-05-27 19:03 ` [PATCH 3/6] edac, mce_amd_inj: Modify flags attrigute to use string arguments Aravind Gopalakrishnan
2015-05-29 13:49 ` Borislav Petkov
2015-05-29 18:20 ` Aravind Gopalakrishnan
2015-05-29 19:05 ` Borislav Petkov
2015-05-29 19:12 ` Aravind Gopalakrishnan
2015-06-01 19:16 ` Aravind Gopalakrishnan
2015-05-27 19:03 ` [PATCH 4/6] edac, mce_amd_inj: Add capability to trigger apic interrupts Aravind Gopalakrishnan
2015-05-29 15:36 ` Borislav Petkov
2015-05-29 18:27 ` Aravind Gopalakrishnan
2015-05-29 19:18 ` Borislav Petkov
2015-05-27 19:03 ` [PATCH 5/6] edac, mce_amd_inj: Add README file Aravind Gopalakrishnan
2015-05-29 15:38 ` Borislav Petkov
2015-05-29 18:29 ` Aravind Gopalakrishnan [this message]
2015-05-27 19:03 ` [PATCH 6/6] edac, mce_amd_inj: Inject errors on NBC for bank 4 errors Aravind Gopalakrishnan
2015-05-29 16:00 ` Borislav Petkov
2015-05-29 18:52 ` Aravind Gopalakrishnan
2015-05-29 19:23 ` Borislav Petkov
2015-05-29 19:27 ` Aravind Gopalakrishnan
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=5568B006.9090804@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.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 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.