From: "Bjørn Mork" <bjorn@mork.no>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "'Eric Dumazet'" <eric.dumazet@gmail.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] usbnet: Fix dma setup for fragmented packets that need a pad byte appended.
Date: Tue, 14 Jan 2014 19:51:10 +0100 [thread overview]
Message-ID: <87mwiy75y9.fsf@nemi.mork.no> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D45B744@AcuExch.aculab.com> (David Laight's message of "Tue, 14 Jan 2014 17:28:27 +0000")
David Laight <David.Laight@ACULAB.COM> writes:
> From: Bjørn Mork [mailto:bjorn@mork.no]
>> David Laight <David.Laight@ACULAB.COM> writes:
>>
>> > I couldn't find the original patch anywhere!
>> > I did do quite a lot of looking as well - if I'd found it I've
>> > have done something else.
>>
>> You obviously haven't looked the one place you are supposed to always
>> look before submitting *anything*:
>> https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=fdc3452cd2c7b2bfe0f378f92123f4f9
>> a98fa2bd
>>
>> I am not impressed...
>
> Without the commit id that is rather hard.
I suggest you stop this nonsense now.
If you are going to submit a patch for "net", then the last thing you do
is check out net/master and rebase on top of it. If you had done so,
then you would have noticed the conflict. You never need to know the
commit id. Where the heck do you think I got it?
> Does anything even get there without manual actions.
> usb patches sit in a hidden limbo for ages.
>
> I looked through my mailboxes and searched for the thread - but only
> found the messages that included the one that said you'd send a patch
> soon.
>
> What I still don't understand is how I found the patch before!
Does it matter? You obviously knew you were posting a duplicate. There
is no excuse for that. Duplicates do *not* help. Whether you are able
to find the original or not doesn't matter. The rest of the world is.
Duplicate are confusing. Confusion cause delays and noise. I assume
you don't want either.
> The fact that work make me use outluck makes searching mail locally
> almost impossible.
Your lack of proper tools is your problem...
Now I know I come out a bit harsh. I can't help it. It's not that I
care much about whether or not I am credited for this oneliner, and you
did credit me in any case. But this whole discussion is so completely
unnecessary. Just use patchwork to track the status of patches you are
interested in. If you can't find a patch there, then YOU are doing
something wrong. It's as simple as that. No excuse.
Bjørn
prev parent reply other threads:[~2014-01-14 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 11:16 [PATCH] usbnet: Fix dma setup for fragmented packets that need a pad byte appended David Laight
2014-01-14 14:41 ` Eric Dumazet
2014-01-14 14:48 ` David Laight
2014-01-14 15:48 ` Bjørn Mork
2014-01-14 17:28 ` David Laight
2014-01-14 18:51 ` Bjørn Mork [this message]
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=87mwiy75y9.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=David.Laight@ACULAB.COM \
--cc=eric.dumazet@gmail.com \
--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).