From: Greg KH <gregkh@linuxfoundation.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH for-4.14.y 0/5] e1000e: Upstream fixes for linux-4.14.y
Date: Tue, 28 Nov 2017 10:24:52 +0100 [thread overview]
Message-ID: <20171128092452.GE7891@kroah.com> (raw)
In-Reply-To: <CAMi1Hd1nhFjKS6YKsFjBehk5xCxn14f43-uEUDHt59q5uxCkug@mail.gmail.com>
On Mon, Nov 27, 2017 at 06:39:47PM +0530, Amit Pundir wrote:
> + Jeff and intel-wired-lan (moderated) mailing list.
>
> On 27 November 2017 at 18:29, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Mon, Nov 27, 2017 at 06:23:32PM +0530, Amit Pundir wrote:
> >> Hi Greg,
> >>
> >> Found few e100e upstream fixes from Benjamin Poirier in lede
> >> source tree, https://git.lede-project.org/?p=source.git, and
> >> these fixes seem reasonable enough for 4.14.y too.
> >>
> >> Also submitting an e1000e buffer overrun fix by Sasha Neftin.
> >>
> >> Cherry-picked and build tested for linux v4.14.2 for ARCH=arm/arm64.
> >
> >
> > Any reason you did not cc: the maintainers for this driver and their
> > mailing list?
>
> No reason at all. Thanks for pointing that out. It didn't occur to me
> to do that. I was marking only patch authors in cover letters so far.
> I'll start adding respective maintainers and mailing list going
> forward.
Thanks, please do that. All now queued up.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: Benjamin Poirier <bpoirier@suse.com>,
Sasha Neftin <sasha.neftin@intel.com>,
Stable <stable@vger.kernel.org>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH for-4.14.y 0/5] e1000e: Upstream fixes for linux-4.14.y
Date: Tue, 28 Nov 2017 10:24:52 +0100 [thread overview]
Message-ID: <20171128092452.GE7891@kroah.com> (raw)
In-Reply-To: <CAMi1Hd1nhFjKS6YKsFjBehk5xCxn14f43-uEUDHt59q5uxCkug@mail.gmail.com>
On Mon, Nov 27, 2017 at 06:39:47PM +0530, Amit Pundir wrote:
> + Jeff and intel-wired-lan (moderated) mailing list.
>
> On 27 November 2017 at 18:29, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Mon, Nov 27, 2017 at 06:23:32PM +0530, Amit Pundir wrote:
> >> Hi Greg,
> >>
> >> Found few e100e upstream fixes from Benjamin Poirier in lede
> >> source tree, https://git.lede-project.org/?p=source.git, and
> >> these fixes seem reasonable enough for 4.14.y too.
> >>
> >> Also submitting an e1000e buffer overrun fix by Sasha Neftin.
> >>
> >> Cherry-picked and build tested for linux v4.14.2 for ARCH=arm/arm64.
> >
> >
> > Any reason you did not cc: the maintainers for this driver and their
> > mailing list?
>
> No reason at all. Thanks for pointing that out. It didn't occur to me
> to do that. I was marking only patch authors in cover letters so far.
> I'll start adding respective maintainers and mailing list going
> forward.
Thanks, please do that. All now queued up.
greg k-h
next prev parent reply other threads:[~2017-11-28 9:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 12:53 [PATCH for-4.14.y 0/5] e1000e: Upstream fixes for linux-4.14.y Amit Pundir
2017-11-27 12:53 ` [PATCH for-4.14.y 1/5] e1000e: Fix error path in link detection Amit Pundir
2017-11-27 12:53 ` [PATCH for-4.14.y 2/5] e1000e: Fix return value test Amit Pundir
2017-11-27 12:53 ` [PATCH for-4.14.y 3/5] e1000e: Separate signaling for link check/link up Amit Pundir
2017-11-27 12:53 ` [PATCH for-4.14.y 4/5] e1000e: Avoid receiver overrun interrupt bursts Amit Pundir
2017-11-27 12:53 ` [PATCH for-4.14.y 5/5] e1000e: fix buffer overrun while the I219 is processing DMA transactions Amit Pundir
2017-11-27 12:59 ` [PATCH for-4.14.y 0/5] e1000e: Upstream fixes for linux-4.14.y Greg KH
2017-11-27 13:09 ` [Intel-wired-lan] " Amit Pundir
2017-11-27 13:09 ` Amit Pundir
2017-11-28 9:24 ` Greg KH [this message]
2017-11-28 9:24 ` Greg KH
2017-11-27 13:36 ` [Intel-wired-lan] " Amit Pundir
2017-11-27 13:36 ` Amit Pundir
2017-12-04 15:47 ` Christian Hesse
2017-12-04 18:37 ` Greg KH
2017-12-05 7:23 ` Christian Hesse
2017-12-05 7:35 ` Greg KH
2017-12-11 21:58 ` Christian Hesse
2017-12-18 11:59 ` Greg KH
2017-12-19 1:10 ` Benjamin Poirier
2017-12-19 23:27 ` Jeff Kirsher
2018-01-01 3:53 ` Benjamin Poirier
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=20171128092452.GE7891@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=intel-wired-lan@osuosl.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.