linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH net-next 5/7] net:fec: add support for dumping transmit ring on timeout
Date: Tue, 29 Apr 2014 16:04:04 +0100	[thread overview]
Message-ID: <20140429150403.GC26756@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAHrpEqQL7LviXA4_NLNwSBoW84W_vbnzWkc9At5QBqUkqu63yw@mail.gmail.com>

On Tue, Apr 29, 2014 at 09:54:09AM -0500, Frank Li wrote:
> On Tue, Apr 29, 2014 at 9:32 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Tue, Apr 29, 2014 at 09:22:13AM -0500, Frank Li wrote:
> >> On Tue, Apr 29, 2014 at 9:15 AM, Russell King - ARM Linux
> >> <linux@arm.linux.org.uk> wrote:
> >> > On Tue, Apr 29, 2014 at 02:01:54PM +0000, David Laight wrote:
> >> >> From: Frank ...
> >> >> > > You probably want the read and write indexes as well.
> >> >> >
> >> >> >                      bdp == fep->cur_tx ? 'S' : ' ',
> >> >> >                      bdp == fep->dirty_tx ? 'H' : ' ',
> >> >> >
> >> >> > Above code already print read and write index. 'S', 'H'
> >> >>
> >> >> Gah I must be asleep!
> >> >> Something made be think that was to do with the ring ownership bit!
> >> >
> >> > Err, what's going on... this is my patch.  If it's been submitted by
> >> > others, why wasn't its submission at least Cc'd to me?
> >>
> >> I added " --to rmk+kernel at arm.linux.org.uk" when I send patch.
> >> I don't know what's wrong.
> >
> > Yes... I guess you don't know what went wrong because you'll never know
> > if it failed to be delivered, because you sent them with an envelope
> > address of "b20596 at shlinux1.ap.freescale.net" which doesn't actually
> > exist.  Therefore, DSNs can't be returned to you.
> >
> >> I ask you if need someone help send to david millar before.
> >
> > You did, but I didn't agree to it.  I did point out that they need a
> > certain amount of rework first:
> 
> Sorry, I miss understood your means.
> I will stop working on this.

I'd just like to see what you're doing.  Note that your submission also
didn't get through the linux-arm-kernel list either, so I didn't get it
via that path either.

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

  reply	other threads:[~2014-04-29 15:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1398773350-7293-1-git-send-email-Frank.Li@freescale.com>
     [not found] ` <1398773350-7293-5-git-send-email-Frank.Li@freescale.com>
2014-04-29 13:38   ` [PATCH net-next 5/7] net:fec: add support for dumping transmit ring on timeout David Laight
2014-04-29 13:57     ` Frank Li
2014-04-29 14:01       ` David Laight
2014-04-29 14:15         ` Russell King - ARM Linux
2014-04-29 14:22           ` Frank Li
2014-04-29 14:30             ` Frank Li
2014-04-29 14:32             ` Russell King - ARM Linux
2014-04-29 14:54               ` Frank Li
2014-04-29 15:04                 ` Russell King - ARM Linux [this message]
2014-04-29 15:11                   ` Frank Li
2014-04-30  6:22                     ` Shawn Guo
2014-04-29 14:18         ` Frank Li
2014-04-29 14:23           ` David Laight
2014-04-29 14:38             ` Russell King - ARM Linux

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=20140429150403.GC26756@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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).