From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] SH: No need to explicitly include <linux/rwlock.h>.
Date: Tue, 02 Mar 2010 03:13:47 +0000 [thread overview]
Message-ID: <20100302031347.GE20256@linux-sh.org> (raw)
On Sat, Feb 27, 2010 at 01:35:08PM -0500, Robert P. J. Day wrote:
>
> Since <linux/spinlock.h> already includes <linux/rwlock.h>, and the
> latter file will warn about not having included the former file
> anyway, there is no value in including rwlock.h explicitly.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
Applied.
next reply other threads:[~2010-03-02 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 3:13 Paul Mundt [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-27 18:35 [PATCH] SH: No need to explicitly include <linux/rwlock.h> Robert P. J. Day
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=20100302031347.GE20256@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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.