All of lore.kernel.org
 help / color / mirror / Atom feed
From: perry.hooker@gmail.com (Perry Hooker)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Patch Question
Date: Wed, 19 Apr 2017 09:54:33 -0600	[thread overview]
Message-ID: <CAO62RXdj24OPnNzXraDsrp+zw9PnwaBY5wJ+2CYmBix+WzZK_w@mail.gmail.com> (raw)
In-Reply-To: <20170419001132.GA15282@eros>

> Dan Carpenter is very good at what he dose. I would be hesitant to
> ever call him or anyone as experienced 'flat-out incorrect'.

Mr. Carpenter's first assertion that the patch "introduces bugs" was
incorrect by his own admission:
https://lkml.org/lkml/2017/3/22/120

Additionally, his assertion that the "buff likely is just a regular
ieee80211_hdr struct" was also incorrect.

> In your comments you in no way display that you understand exactly
> what the code is doing and why it should by changed. Your initial
> patch does not have an appropriate changelog message, please read
> Documentation/process/submitting-patches.rst (section 2 Describing
> your changes).

I disagree. I've written both where the buffer is allocated and where
it's filled, and why the contents need to be converted to
little-endian byte order. Can you comment on whether my analysis is
correct?

Also, here are several commits that fix similar issues with similar
changelog messages:
https://github.com/torvalds/linux/commit/a15505e69cd2f8d0ebf566cd5c5838bd5c2d56e3
https://github.com/torvalds/linux/commit/47910a49db876397150b9754bc66f0c179448854
https://github.com/torvalds/linux/commit/af27e01cfcfcdf7f45488e023b474eb6de5f732e

Can you comment on what's considered an "appropriate changelog message?"

> A more subtle point - you may have more success if you do not put
> demands onto people (eg can you explain this..) but rather write out
> your understanding of the code explaining why your hold the views you
> do. Others can then comment or this, agreeing or disagreeing as the
> case may be. People like to help by giving their knowledge, no one
> likes doing chores.

As I mentioned (and is contained in the thread), I've written out my
understanding of where the buffer is allocated, where it's filled, and
why the conversion needs to happen.
At this point, no one has commented on the accuracy of my analysis.
Such comments are exactly what I'm hoping for (and what I requested -
not "demanded" - in my replies).

So, if you can provide some useful analysis, I'd be happy to listen.

  reply	other threads:[~2017-04-19 15:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 23:28 Patch Question Perry Hooker
2017-04-17 23:48 ` Mandeep Sandhu
2017-04-17 23:58 ` Tobin C. Harding
2017-04-18 23:07   ` Perry Hooker
2017-04-19  0:11     ` Tobin C. Harding
2017-04-19 15:54       ` Perry Hooker [this message]
2017-04-19 16:13         ` Greg KH
2017-04-19 16:46           ` Perry Hooker
2017-04-19 20:48             ` Lino Sanfilippo
2017-04-19 13:27 ` Lino Sanfilippo
2017-04-19 15:41   ` Perry Hooker
  -- strict thread matches above, loose matches on Subject: below --
2005-09-22  3:01 Alejandro Bonilla Beeche
2005-09-22  4:32 ` Randy.Dunlap
2005-09-22  6:33   ` Jesper Juhl

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=CAO62RXdj24OPnNzXraDsrp+zw9PnwaBY5wJ+2CYmBix+WzZK_w@mail.gmail.com \
    --to=perry.hooker@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.