From: Greg KH <gregkh@linuxfoundation.org>
To: meljbao@gmail.com
Cc: stable@vger.kernel.org, Sasha Neftin <sasha.neftin@intel.com>,
Dvora Fuxbrumer <dvorax.fuxbrumer@linux.intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Subject: Re: [PATCH] igc: Remove _I_PHY_ID checking for i225 devices
Date: Thu, 11 Aug 2022 15:48:43 +0200 [thread overview]
Message-ID: <YvUIu/ROCzcoOPhE@kroah.com> (raw)
In-Reply-To: <1bb5e092-310b-26fa-38f7-fb797b1cd995@gmail.com>
On Thu, Aug 11, 2022 at 06:19:20PM +0800, meljbao@gmail.com wrote:
> On 8/11/22 4:52 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Thu, Aug 11, 2022 at 04:39:51PM +0800, Linjun Bao wrote:
> > > commit 7c496de538ee ("igc: Remove _I_PHY_ID checking") upstream,
> > > backported to stable kernel 5.4 to support i225 Ethernet adapters.
> > >
> > > Signed-off-by: Linjun Bao <meljbao@gmail.com>
> >
> > What happened to the original commit message and signed off by lines,
> > and why not cc: everyone involved in the original commit also?
> >
> I wrongly re-send this commit to mainline initially, then Tony guided me
> submitting to the stable tree with Option#3 [1]. Sorry I did not involve
> everyone in the original commit which I should. I re-send this commit
> because I encounter probe failure with i225-LM Ethernet card on liuux-5.4,
> and the original commit could not be applied to 5.4 directly, and this
> duplicated patch has been tested with i225-LM. I would like this commit is
> backported to linux-5.4, please correct me if I am doing the wrong thing.
>
> Regards
> Joseph
>
> [1] https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#procedure-for-submitting-patches-to-the-stable-tree
The original commit worked just fine, why not just send that?
I've now queued it up, thanks.
greg k-h
prev parent reply other threads:[~2022-08-11 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 8:39 [PATCH] igc: Remove _I_PHY_ID checking for i225 devices Linjun Bao
2022-08-11 8:52 ` Greg KH
2022-08-11 10:19 ` meljbao
2022-08-11 13:48 ` Greg KH [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=YvUIu/ROCzcoOPhE@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anthony.l.nguyen@intel.com \
--cc=dvorax.fuxbrumer@linux.intel.com \
--cc=meljbao@gmail.com \
--cc=sasha.neftin@intel.com \
--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.