From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Anca Emanuel <anca.emanuel@gmail.com>
Cc: Mark Einon <mark.einon@gmail.com>,
STAGING SUBSYSTEM <devel@driverdev.osuosl.org>,
LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, stable <stable@vger.kernel.org>
Subject: Re: [PATCH RESEND] staging: et131x: Fix errors caused by phydev->addr accesses before initialisation
Date: Mon, 11 Aug 2014 13:39:59 +0800 [thread overview]
Message-ID: <20140811053959.GD13727@kroah.com> (raw)
In-Reply-To: <CAJL_dMub6FN+HvueQ4ZJCT2TPi9-86x8VF2hG00K8CDm5bR7rw@mail.gmail.com>
On Mon, Aug 11, 2014 at 12:32:55AM +0300, Anca Emanuel wrote:
> Do you have this hardware ? And did you test this ?
Mark is the maintainer of this driver, I assume he has the hardware, if
not, I don't care, I trust him :)
> How can you cc stable without an Tested by somebody else ?
Since when is a tested-by a requirement for a stable@ marking? Please
read Documentation/stable_kernel_rules.txt for the details.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Anca Emanuel <anca.emanuel@gmail.com>
Cc: STAGING SUBSYSTEM <devel@driverdev.osuosl.org>,
Mark Einon <mark.einon@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH RESEND] staging: et131x: Fix errors caused by phydev->addr accesses before initialisation
Date: Mon, 11 Aug 2014 13:39:59 +0800 [thread overview]
Message-ID: <20140811053959.GD13727@kroah.com> (raw)
In-Reply-To: <CAJL_dMub6FN+HvueQ4ZJCT2TPi9-86x8VF2hG00K8CDm5bR7rw@mail.gmail.com>
On Mon, Aug 11, 2014 at 12:32:55AM +0300, Anca Emanuel wrote:
> Do you have this hardware ? And did you test this ?
Mark is the maintainer of this driver, I assume he has the hardware, if
not, I don't care, I trust him :)
> How can you cc stable without an Tested by somebody else ?
Since when is a tested-by a requirement for a stable@ marking? Please
read Documentation/stable_kernel_rules.txt for the details.
thanks,
greg k-h
next prev parent reply other threads:[~2014-08-11 5:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 21:16 [PATCH RESEND] staging: et131x: Fix errors caused by phydev->addr accesses before initialisation Mark Einon
2014-08-10 21:16 ` Mark Einon
2014-08-10 21:32 ` Anca Emanuel
2014-08-10 21:32 ` Anca Emanuel
2014-08-11 5:39 ` gregkh [this message]
2014-08-11 5:39 ` gregkh
2014-08-11 7:35 ` Mark Einon
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=20140811053959.GD13727@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anca.emanuel@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.einon@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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 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.