From: Chen Gong <gong.chen@linux.intel.com>
To: Matthew Garrett <mjg@redhat.com>
Cc: tony.luck@intel.com, linux-kernel@vger.kernel.org,
mikew@google.com, saguchi@redhat.com
Subject: Re: [PATCH] efi: Avoid sysfs spew on reboot and panic
Date: Fri, 23 Sep 2011 14:41:25 +0800 [thread overview]
Message-ID: <4E7C2A15.80703@linux.intel.com> (raw)
In-Reply-To: <20110922131504.GA11990@srcf.ucam.org>
于 2011/9/22 21:15, Matthew Garrett 写道:
> On Thu, Sep 22, 2011 at 10:21:58AM +0800, Chen Gong wrote:
>> 于 2011/9/21 20:40, Matthew Garrett 写道:
>>> On Wed, Sep 21, 2011 at 11:31:40AM +0800, Chen Gong wrote:
>>>>> mutex_lock(&psinfo->buf_mutex);
>>>>> memcpy(psinfo->buf, buf, size);
>>>>> - id = psinfo->write(type, 0, size, psinfo);
>>>>> + id = psinfo->write(type, 0, KMSG_DUMP_UNKNOWN, size, psinfo);
>>>>
>>>> I can't say it is wrong because no real caller for this function, but I can't
>>>> say it is right, yet. KMSG_DUMP_UNKNOWN here looks too arbirary. Do you have
>>>> any reason to use this type here ?
>>>
>>> If a function calls pstore_write() directly then we have no type to
>>> associate with it. It seems worth making this explicit.
>>
>> Yep, that's the point. We hope to get a more reasonable method to do it, not
>> any assumption.
>
> I'm afraid I don't understand. Could you give an example of how you
> think this should look?
>
If you insist on your design, I prefer deleting the function pstore_write before
applying your patch. We all know no real users to call this function,
every backend will register Its own callback, so this function is useless at all.
next prev parent reply other threads:[~2011-09-23 6:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 21:07 [PATCH] efi: Avoid sysfs spew on reboot and panic Matthew Garrett
2011-09-21 3:31 ` Chen Gong
2011-09-21 12:40 ` Matthew Garrett
2011-09-22 2:21 ` Chen Gong
2011-09-22 13:15 ` Matthew Garrett
2011-09-23 6:41 ` Chen Gong [this message]
2011-09-23 17:11 ` Luck, Tony
2012-01-12 18:33 ` Seiji Aguchi
2011-09-21 13:01 ` Seiji Aguchi
-- strict thread matches above, loose matches on Subject: below --
2012-03-07 22:49 Seiji Aguchi
[not found] <32727E9A83EE9A42A1F0906295A3A77B2E598C0A91@USINDEVS01.corp.hds.com>
2012-04-13 14:37 ` Seiji Aguchi
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=4E7C2A15.80703@linux.intel.com \
--to=gong.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=mjg@redhat.com \
--cc=saguchi@redhat.com \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).