From: Danny Kukawka <danny.kukawka@bisect.de>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Chris Ball <cjb@laptop.org>, Olof Johansson <olof@lixom.net>,
Stephen Warren <swarren@nvidia.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sdhci-tegra: fix linux/module.h included twice
Date: Wed, 15 Feb 2012 21:45:42 +0100 [thread overview]
Message-ID: <201202152145.43344.danny.kukawka@bisect.de> (raw)
In-Reply-To: <4F3C032D.7080905@windriver.com>
On Mittwoch, 15. Februar 2012, Paul Gortmaker wrote:
> On 12-02-15 12:54 PM, Danny Kukawka wrote:
> > Remove double include of linux/module.h.
> >
> > Signed-off-by: Danny Kukawka <danny.kukawka@bisect.de>
>
> Hi Danny,
>
> We've already got these covered all in one go.
>
> https://lkml.org/lkml/2012/2/4/134
Okay, I checked mainline and linux-next and did a fast search over the Subject
on the ML and couldn't find these fixes.
Where they already applied to a tree?
Then you may want to ignore these of my mails:
- [PATCH] sdhci-tegra: fix linux/module.h included twice
- [PATCH] dwc3: linux/module.h included twice
-> https://lkml.org/lkml/2012/2/15/309
- [PATCH] drivers/dma: linux/module.h included twice
-> https://lkml.org/lkml/2012/2/15/351
- [PATCH] adp1653: included linux/module.h twice
-> https://lkml.org/lkml/2012/2/15/352
- [PATCH] Staging: sm7xx/smtcfb.c included linux/module.h twice
-> https://lkml.org/lkml/2012/2/15/355
Danny
prev parent reply other threads:[~2012-02-15 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 17:54 [PATCH] sdhci-tegra: fix linux/module.h included twice Danny Kukawka
2012-02-15 18:38 ` Olof Johansson
2012-02-15 19:10 ` Paul Gortmaker
2012-02-15 20:45 ` Danny Kukawka [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=201202152145.43344.danny.kukawka@bisect.de \
--to=danny.kukawka@bisect.de \
--cc=cjb@laptop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=paul.gortmaker@windriver.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=swarren@nvidia.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