linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ozgur Karatas <okaratas@member.fsf.org>
To: Paul Bolle <pebolle@tiscali.nl>,
	johannes <johannes@sipsolutions.net>,
	David Miller <davem@davemloft.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] net: wireless: fix to uses struct
Date: Thu, 22 Dec 2016 01:16:16 +0200	[thread overview]
Message-ID: <489331482362176@web18m.yandex.ru> (raw)
In-Reply-To: <1482361572.28171.8.camel@tiscali.nl>


22.12.2016, 01:06, "Paul Bolle" <pebolle@tiscali.nl>:
> On Thu, 2016-12-22 at 01:50 +0300, Ozgur Karatas wrote:
>>  I don't have a problem with C programming
>
> I'm sorry, but you do need to learn C, at a basic level, first.

Hmm, I don't like to discussion but I'm an assertive on C/C++.
So, I'm not into the Linux kernel, I writing code with C/C++ for many years. 
I'm having trouble using Linux tools and trying to learn git/diff/format-patch/etc. 

Also, I'm reading over 600 e-mails per day and I'm reading to Documentation (kernel). I learn :)

I don't have to problem with C, you can see my early codes and software (github).

I need to get a good sense of the coding style and Documentation.

And thank you.

Regards

> Paul Bolle

~Ozgur

  reply	other threads:[~2016-12-21 23:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 22:23 [PATCH 2/2] net: wireless: fix to uses struct Ozgur Karatas
2016-12-21 22:33 ` Paul Bolle
2016-12-21 22:50   ` Ozgur Karatas
2016-12-21 23:01     ` Ozgur Karatas
2016-12-21 23:06     ` Paul Bolle
2016-12-21 23:16       ` Ozgur Karatas [this message]
2016-12-22  5:18 ` kbuild test robot
2016-12-22  7:05 ` kbuild test robot
2016-12-22  9:37 ` Arend Van Spriel

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=489331482362176@web18m.yandex.ru \
    --to=okaratas@member.fsf.org \
    --cc=davem@davemloft.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=tglx@linutronix.de \
    /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).