From: SeongJae Park <sj38.park@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Lauri Hintsala <lauri.hintsala@bluegiga.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: csr: fix coding style
Date: Tue, 23 Oct 2012 11:41:06 +0900 [thread overview]
Message-ID: <CAEjAshqiVPA86fYNehmAEqiiZt0tGBvhu3ntFy+7XA4oLZKtRg@mail.gmail.com> (raw)
In-Reply-To: <CAEjAshoH2CJpnq-mt1TB6XB3i22QM+UeTKzr__ZgjHNUts3odA@mail.gmail.com>
Hello,
I think it was my mistake.
CsrThread is enclosed by macro #ifdef __KERNEL__
and it used by csr_framework_ext.h as CsrThreadHandle type(typedef
used at csr_framework_ext_types.h).
I think that's why I didn't see build failure.
So, I think I should not remove CsrThread.
If there is anything I missed or wrong, Please let me know.
Thnks and Regards.
SeongJae Park.
On Tue, Oct 23, 2012 at 11:13 AM, SeongJae Park <sj38.park@gmail.com> wrote:
> Hello,
>
>
> Thank you very much for your kindness, Greg.
>
> I tried to reply to email-list when I received Lauri's email, but I
> coudln't because my gmail service has some problems.
>
> I'm still newbie, sorry.
>
> I will send new patch that removes whole struct, as soon as
> possible(maybe 4~5 hours later).
>
>
> Thanks and Regards.
> SeongJae Park.
next prev parent reply other threads:[~2012-10-23 2:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 7:55 [PATCH] staging: csr: fix coding style SeongJae Park
2012-10-16 7:13 ` Lauri Hintsala
2012-10-22 20:56 ` Greg KH
2012-10-23 2:13 ` SeongJae Park
2012-10-23 2:41 ` SeongJae Park [this message]
2012-10-23 2:53 ` Greg KH
2012-10-23 3:07 ` SeongJae Park
2012-10-25 6:54 [PATCH] staging: csr: Fix " SeongJae Park
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=CAEjAshqiVPA86fYNehmAEqiiZt0tGBvhu3ntFy+7XA4oLZKtRg@mail.gmail.com \
--to=sj38.park@gmail.com \
--cc=greg@kroah.com \
--cc=lauri.hintsala@bluegiga.com \
--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 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).