public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: David Miller <davem@davemloft.net>
Cc: c0d1n61at3@gmail.com,
	linux-kernel-mentees@lists.linuxfoundation.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [Linux-kernel-mentees][PATCH v2] packet: Fix undefined behavior in bit shift
Date: Thu, 27 Jun 2019 10:52:10 -0600	[thread overview]
Message-ID: <9687ddc6-3bdb-5b2a-2934-ed9c6921551d@linuxfoundation.org> (raw)
In-Reply-To: <20190627.092253.1878691006683087825.davem@davemloft.net>

On 6/27/19 10:22 AM, David Miller wrote:
> From: Shuah Khan <skhan@linuxfoundation.org>
> Date: Wed, 26 Jun 2019 21:32:52 -0600
> 
>> On 6/26/19 9:25 PM, Jiunn Chang wrote:
>>> Shifting signed 32-bit value by 31 bits is undefined.  Changing most
>>> significant bit to unsigned.
>>> Changes included in v2:
>>>     - use subsystem specific subject lines
>>>     - CC required mailing lists
>>>
>>
>> These version change lines don't belong in the change log.
> 
> For networking changes I actually like the change lines to be in the
> commit log.  So please don't stray people this way, thanks.
> 

As a general rule, please don't include change lines in the commit log.
For networking changes that get sent to David and netdev, as David
points out here, he likes them in the commit log, please include them
in the commit log.

I am working on FAQ (Frequently Answered Questions) section for mentees.
I will add this to it.

thanks,
-- Shuah

  reply	other threads:[~2019-06-27 16:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190627010137.5612-1-c0d1n61at3@gmail.com>
2019-06-27  3:25 ` [Linux-kernel-mentees][PATCH v2] packet: Fix undefined behavior in bit shift Jiunn Chang
2019-06-27  3:32   ` Shuah Khan
2019-06-27 16:22     ` David Miller
2019-06-27 16:52       ` Shuah Khan [this message]
2019-06-27 17:05         ` Alexei Starovoitov
2019-06-27 17:08           ` Shuah Khan
2019-06-27 16:57       ` Jiunn Chang
2019-06-27 17:34         ` David Miller
2019-06-27  5:04   ` [Linux-kernel-mentees][PATCH v3] " Jiunn Chang
2019-06-29 18:06   ` [Linux-kernel-mentees][PATCH v2] " David Miller

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=9687ddc6-3bdb-5b2a-2934-ed9c6921551d@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=c0d1n61at3@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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