From: Karsten Keil <isdn@linux-pingi.de>
To: Tejun Heo <tj@kernel.org>
Cc: Tilman Schmidt <tilman@imap.cc>,
David Miller <davem@davemloft.net>,
Hansjoerg Lipp <hjlipp@web.de>,
i4ldeveloper@listserv.isdn4linux.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gigaset: include cleanup cleanup
Date: Sun, 18 Apr 2010 15:31:14 +0200 [thread overview]
Message-ID: <201004181531.14871.isdn@linux-pingi.de> (raw)
In-Reply-To: <4BCA6B8E.9000408@kernel.org>
On Sonntag, 18. April 2010 04:16:46 Tejun Heo wrote:
> Hello,
>
> On 04/17/2010 07:08 AM, Tilman Schmidt wrote:
> > Commit 5a0e3ad causes slab.h to be included twice in many of the
> > Gigaset driver's source files, first via the common include file
> > gigaset.h and then a second time directly. Drop the spares, and
> > use the opportunity to clean up a few more similar cases.
> >
> > Impact: cleanup, no functional change
> > Signed-off-by: Tilman Schmidt <tilman@imap.cc>
> > CC: Tejun Heo <tj@kernel.org>
>
> Acked-by: Tejun Heo <tj@kernel.org>
Acked-by: Karsten Keil <isdn@linux-pingi.de>
>
> Thanks for the clean up.
>
> > Seeing that the "include cleanup" patch triggering this was accepted
> > after the merge window, I have hopes this one will be accepted, too.
>
> Hmm... through which tree should this go through? I can route it
> through percpu but maybe taking the usual isdn patch path would be
> better?
>
I think David Miller will take it.
Karsten
prev parent reply other threads:[~2010-04-18 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 22:08 [PATCH] gigaset: include cleanup cleanup Tilman Schmidt
2010-04-18 2:16 ` Tejun Heo
2010-04-18 9:13 ` David Miller
2010-04-18 13:31 ` Karsten Keil [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=201004181531.14871.isdn@linux-pingi.de \
--to=isdn@linux-pingi.de \
--cc=davem@davemloft.net \
--cc=hjlipp@web.de \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tilman@imap.cc \
--cc=tj@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 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).