From: "Arend van Spriel" <arend@broadcom.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Brett Rudley <brudley@broadcom.com>,
Roland Vossen <rvossen@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
Kan Yan <kanyan@broadcom.com>,
"John W. Linville" <linville@tuxdriver.com>,
Pieter-Paul Giesberts <pieterpg@broadcom.com>,
linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] brcm80211: brcmu_pkt_buf_free_skb() should handle NULL
Date: Tue, 15 May 2012 16:57:10 +0000 [thread overview]
Message-ID: <4FB28AE6.3000700@broadcom.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1205151706360.2356@hadrien>
On 05/15/2012 05:07 PM, Julia Lawall wrote:
>
> 1 - A marker line containing simply "---".
>
> 2 - Any additional comments not suitable for the changelog.
>
I guess that 1 can be omitted when there is no 2. I was just wondering
whether the diff command would end up in the changelog when applying the
patch.
Gr. AvS
WARNING: multiple messages have this Message-ID (diff)
From: "Arend van Spriel" <arend@broadcom.com>
To: "Julia Lawall" <julia.lawall@lip6.fr>
Cc: "Dan Carpenter" <dan.carpenter@oracle.com>,
"Brett Rudley" <brudley@broadcom.com>,
"Roland Vossen" <rvossen@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
"Kan Yan" <kanyan@broadcom.com>,
"John W. Linville" <linville@tuxdriver.com>,
"Pieter-Paul Giesberts" <pieterpg@broadcom.com>,
linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] brcm80211: brcmu_pkt_buf_free_skb() should handle NULL
Date: Tue, 15 May 2012 18:57:10 +0200 [thread overview]
Message-ID: <4FB28AE6.3000700@broadcom.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1205151706360.2356@hadrien>
On 05/15/2012 05:07 PM, Julia Lawall wrote:
>
> 1 - A marker line containing simply "---".
>
> 2 - Any additional comments not suitable for the changelog.
>
I guess that 1 can be omitted when there is no 2. I was just wondering
whether the diff command would end up in the changelog when applying the
patch.
Gr. AvS
next prev parent reply other threads:[~2012-05-15 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 9:00 [patch] brcm80211: brcmu_pkt_buf_free_skb() should handle NULL Dan Carpenter
2012-05-15 9:00 ` Dan Carpenter
2012-05-15 14:21 ` Arend van Spriel
2012-05-15 14:21 ` Arend van Spriel
2012-05-15 14:28 ` Arend van Spriel
2012-05-15 14:28 ` Arend van Spriel
2012-05-15 14:44 ` Dan Carpenter
2012-05-15 14:44 ` Dan Carpenter
2012-05-15 15:07 ` Julia Lawall
2012-05-15 15:07 ` Julia Lawall
2012-05-15 16:57 ` Arend van Spriel [this message]
2012-05-15 16:57 ` 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=4FB28AE6.3000700@broadcom.com \
--to=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=frankyl@broadcom.com \
--cc=julia.lawall@lip6.fr \
--cc=kanyan@broadcom.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=pieterpg@broadcom.com \
--cc=rvossen@broadcom.com \
/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.