From: David Sterba <dsterba@suse.cz>
To: Giel van Schijndel <me@mortis.eu>
Cc: linux-kernel@vger.kernel.org, Armin Schindler <mac@melware.de>,
Karsten Keil <isdn@linux-pingi.de>,
"open list:ISDN SUBSYSTEM" <netdev@vger.kernel.org>
Subject: Re: [PATCH] Fix NUL (\0 or \x00) specification in string
Date: Wed, 7 Jan 2015 13:22:58 +0100 [thread overview]
Message-ID: <20150107122258.GG24104@suse.cz> (raw)
In-Reply-To: <20150106192804.GL4806@salidar.dom.custoft.eu>
On Tue, Jan 06, 2015 at 08:28:04PM +0100, Giel van Schijndel wrote:
> On Mon, Jan 05, 2015 at 16:00:26 +0100, David Sterba wrote:
> > I'm replying to all your recent patches here as they are fixing things
> > reported in http://www.viva64.com/en/b/0299/ . I'ts a good practice to
> > give the credit the reporter.
> >
> > The blogpost also contains analyses of the issues so it could help
> > reviewing the patches.
>
> I guess you suggest I use a 'Reported-(at|by)' line?
A link in the changelog would be enough IMHO.
> Would something like the below suffice? I found similar log entries in the
> commit log, e.g. bf3204cb, except that those add an e-mail address for
> the reporters, which I don't think is necessary in this case.
If you don't have the emails, then rather do not use reported-by.
next prev parent reply other threads:[~2015-01-07 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 18:05 [PATCH] Fix NUL (\0 or \x00) specification in string Giel van Schijndel
2015-01-04 23:04 ` Giel van Schijndel
2015-01-05 15:00 ` David Sterba
2015-01-06 19:28 ` Giel van Schijndel
2015-01-07 12:22 ` David Sterba [this message]
2015-01-07 18:45 ` Andy Shevchenko
2015-01-07 19:10 ` [PATCH RESEND] isdn: fix " Giel van Schijndel
2015-01-12 20:32 ` 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=20150107122258.GG24104@suse.cz \
--to=dsterba@suse.cz \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mac@melware.de \
--cc=me@mortis.eu \
--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;
as well as URLs for NNTP newsgroup(s).