From: David Miller <davem@davemloft.net>
To: stefan@datenfreihafen.org
Cc: netdev@vger.kernel.org, linux-zigbee-devel@lists.sourceforge.net,
alan@signal11.us
Subject: Re: ieee802154: Source addr fix for dgram and some small at86rf230 driver enhancements
Date: Wed, 27 Mar 2013 15:10:37 -0400 (EDT) [thread overview]
Message-ID: <20130327.151037.378525240140621201.davem@davemloft.net> (raw)
In-Reply-To: <20130327185204.GH22584@novatech.datenfreihafen.org>
From: Stefan Schmidt <stefan@datenfreihafen.org>
Date: Wed, 27 Mar 2013 18:52:05 +0000
> Hello.
>
> On Wed, 2013-03-27 at 00:53, David Miller wrote:
>> From: Stefan Schmidt <stefan@datenfreihafen.org>
>> Date: Tue, 26 Mar 2013 22:41:28 +0000
>>
>> > Hello.
>> >
>> > Second version. Changes since version 1:
>> > - Obey 80 chars rules
>> > - Switch logging mode to vdbg to avoid noise
>> > - Remove uneeded might_sleep()
>> >
>> > Thanks Alan, Werner and Alex for the feedback.
>> >
>> > I feel these are ready so I added DaveM and netdev to pick them up if they think
>> > the same.
>>
>> All applied.
>
> Thanks. That was quick. :)
>
> I wonder what happened to the from of two of my commits. Looking at
> your repo they only show up my email address:
>
> https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=1486774d69f6e58da16cdae8f17c77ec6569f711
> https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=028889b0b32064a3a23d6d8d4ef589a42a6d43c7
>
> The one from Stephen is fine
> https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=6364e6ee788ae60f1c2de5c59e39adb157327e6c
>
> The later as an explicit from as he was the author and I just the
> sender. For the two problematic ones git am should have picked up the
> normal mail from header, no?
I don't understand what the problem is.
The first two patches list you as the author, as that is the sender in
the From: field.
Oh, I see, the name, have a look at:
http://patchwork.ozlabs.org/patch/231579/
That's where I take the patches from, click on Download "mbox" and you'll
see that it gave me the headers as:
Date: Tue, 26 Mar 2013 12:41:30 -0000
From: stefan@datenfreihafen.org
next prev parent reply other threads:[~2013-03-27 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 22:41 ieee802154: Source addr fix for dgram and some small at86rf230 driver enhancements Stefan Schmidt
[not found] ` <1364337691-20163-1-git-send-email-stefan-OrPQZGeq07wqhVmZOOOmNx2eb7JE58TQ@public.gmane.org>
2013-03-26 22:41 ` [PATCH 1/3] ieee802154/dgram: Pass source address in dgram_recvmsg Stefan Schmidt
2013-03-26 22:41 ` [PATCH 2/3] ieee802154/at86rf230: Implement hardware address filter callback Stefan Schmidt
2013-03-26 22:41 ` [PATCH 3/3] ieee802154/at86rf230: Fix register names for RX_AACK_ON and TX_ARET_ON Stefan Schmidt
2013-03-27 4:53 ` ieee802154: Source addr fix for dgram and some small at86rf230 driver enhancements David Miller
2013-03-27 18:52 ` Stefan Schmidt
2013-03-27 19:10 ` David Miller [this message]
[not found] ` <20130327.151037.378525240140621201.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2013-03-27 21:21 ` Stefan Schmidt
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=20130327.151037.378525240140621201.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@signal11.us \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=stefan@datenfreihafen.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).