From: Liam Girdwood <Liam.Girdwood@wolfsonmicro.com>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] AC97 plugin suspend/resume
Date: Tue, 04 Jan 2005 15:28:46 +0000 [thread overview]
Message-ID: <1104852526.9143.351.camel@cearnarfon> (raw)
In-Reply-To: <41DAB13E.40208@didntduck.org>
On Tue, 2005-01-04 at 15:07, Brian Gerst wrote:
> There is really no reason to add these fields if they are NULL. Zero
> (or NULL for pointers) is the default for all unspecified fields, and it
> is kernel convention to use this feature to reduce clutter.
>
Ok, patch 2/2 can be safely ignored. It was added for clarity.
Liam
prev parent reply other threads:[~2005-01-04 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 14:50 [PATCH 2/2] AC97 plugin suspend/resume Liam Girdwood
2005-01-04 15:07 ` Brian Gerst
2005-01-04 15:28 ` Liam Girdwood [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=1104852526.9143.351.camel@cearnarfon \
--to=liam.girdwood@wolfsonmicro.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.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.