From: Andrew Morton <akpm@linux-foundation.org>
To: Alexandre Bounine <alexandre.bounine@idt.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rapidio: apply RX/TX enable to active switch ports only
Date: Fri, 24 Aug 2012 14:04:19 -0700 [thread overview]
Message-ID: <20120824140419.2b3a9623.akpm@linux-foundation.org> (raw)
In-Reply-To: <1345559035-25879-2-git-send-email-alexandre.bounine@idt.com>
On Tue, 21 Aug 2012 10:23:55 -0400
Alexandre Bounine <alexandre.bounine@idt.com> wrote:
> Modify RIO enumeration to apply RX/TX enable operations only to active
> switch ports. This will leave inactive ports in condition consistent with
> their state.
It's unclear (to me) what the effects of this are. Does it fix some
user-visible malfunction? Or is it just some nice-to-have thing? Or
what?
> This patch is applicable to kernel versions starting from v2.6.35.
Is that a recommendation that such a backport be performed? If so,
please provide the reasoning.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Alexandre Bounine <alexandre.bounine@idt.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Matt Porter <mporter@kernel.crashing.org>
Subject: Re: [PATCH] rapidio: apply RX/TX enable to active switch ports only
Date: Fri, 24 Aug 2012 14:04:19 -0700 [thread overview]
Message-ID: <20120824140419.2b3a9623.akpm@linux-foundation.org> (raw)
In-Reply-To: <1345559035-25879-2-git-send-email-alexandre.bounine@idt.com>
On Tue, 21 Aug 2012 10:23:55 -0400
Alexandre Bounine <alexandre.bounine@idt.com> wrote:
> Modify RIO enumeration to apply RX/TX enable operations only to active
> switch ports. This will leave inactive ports in condition consistent with
> their state.
It's unclear (to me) what the effects of this are. Does it fix some
user-visible malfunction? Or is it just some nice-to-have thing? Or
what?
> This patch is applicable to kernel versions starting from v2.6.35.
Is that a recommendation that such a backport be performed? If so,
please provide the reasoning.
next prev parent reply other threads:[~2012-08-24 21:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 14:23 [PATCH] rapidio/tsi721: modify mport name assignment Alexandre Bounine
2012-08-21 14:23 ` Alexandre Bounine
2012-08-21 14:23 ` [PATCH] rapidio: apply RX/TX enable to active switch ports only Alexandre Bounine
2012-08-21 14:23 ` Alexandre Bounine
2012-08-24 21:04 ` Andrew Morton [this message]
2012-08-24 21:04 ` Andrew Morton
2012-08-27 13:01 ` Bounine, Alexandre
2012-08-27 13:01 ` Bounine, Alexandre
2012-08-24 21:02 ` [PATCH] rapidio/tsi721: modify mport name assignment Andrew Morton
2012-08-24 21:02 ` Andrew Morton
2012-08-27 14:49 ` Bounine, Alexandre
2012-08-27 14:49 ` Bounine, Alexandre
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=20120824140419.2b3a9623.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alexandre.bounine@idt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 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.