From: Stefano Brivio <sbrivio@redhat.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] how to submit fixes for i40e/i40evf?
Date: Sat, 26 Aug 2017 00:28:52 +0200 [thread overview]
Message-ID: <20170826002852.751d5f07@elisabeth> (raw)
In-Reply-To: <CAKgT0UcLAw0958zJ4o9V9Vyamvd1mBQX1+9GAaZw-hZubMqXnw@mail.gmail.com>
On Fri, 25 Aug 2017 15:10:08 -0700
Alexander Duyck <alexander.duyck@gmail.com> wrote:
> On Fri, Aug 25, 2017 at 1:52 PM, Stefano Brivio <sbrivio@redhat.com> wrote:
>
> [...]
>
> > Once patches reach Intel's patchwork, will they need to wait for some
> > kind of periodically scheduled pull request process?
>
> Once in the patchwork they go through testing and after they have
> passed testing Jeff will try to push them to Dave.
Ok, the whole part above is clear, thanks a lot for clarifying.
> > I don't know if a process is actually defined at this level of detail,
> > but still I feel it's wrong that an obvious fix for a potential crash is
> > waiting in some sort of limbo for 10 days now. Sure, worse things
> > happen in the world, but I can't understand what this patch is waiting
> > for.
>
> Well in the case of your patch it was rejected as it didn't apply to
> Jeff's tree
It actually did when I posted it.
> and conflicted with Jacob Keller's patch. He submitted a v2 on Tuesday
> which has only been applied for a few days. Once it receives a
> "Tested-by:"
Which, if I understood correctly, only comes after some internal testing
process, right?
> it will be ready for submission assuming it passes testing.
Now that patch is again in a v2 pull request for net-next, without the
changes I suggested for the commit message. And the same exact code
changes were around for two weeks. IMHO there's room for improvement,
so to speak.
> I hope that helps to clarify things.
It did to some extent, and thanks again for that.
--
Stefano
WARNING: multiple messages have this Message-ID (diff)
From: Stefano Brivio <sbrivio@redhat.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Netdev <netdev@vger.kernel.org>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] how to submit fixes for i40e/i40evf?
Date: Sat, 26 Aug 2017 00:28:52 +0200 [thread overview]
Message-ID: <20170826002852.751d5f07@elisabeth> (raw)
In-Reply-To: <CAKgT0UcLAw0958zJ4o9V9Vyamvd1mBQX1+9GAaZw-hZubMqXnw@mail.gmail.com>
On Fri, 25 Aug 2017 15:10:08 -0700
Alexander Duyck <alexander.duyck@gmail.com> wrote:
> On Fri, Aug 25, 2017 at 1:52 PM, Stefano Brivio <sbrivio@redhat.com> wrote:
>
> [...]
>
> > Once patches reach Intel's patchwork, will they need to wait for some
> > kind of periodically scheduled pull request process?
>
> Once in the patchwork they go through testing and after they have
> passed testing Jeff will try to push them to Dave.
Ok, the whole part above is clear, thanks a lot for clarifying.
> > I don't know if a process is actually defined at this level of detail,
> > but still I feel it's wrong that an obvious fix for a potential crash is
> > waiting in some sort of limbo for 10 days now. Sure, worse things
> > happen in the world, but I can't understand what this patch is waiting
> > for.
>
> Well in the case of your patch it was rejected as it didn't apply to
> Jeff's tree
It actually did when I posted it.
> and conflicted with Jacob Keller's patch. He submitted a v2 on Tuesday
> which has only been applied for a few days. Once it receives a
> "Tested-by:"
Which, if I understood correctly, only comes after some internal testing
process, right?
> it will be ready for submission assuming it passes testing.
Now that patch is again in a v2 pull request for net-next, without the
changes I suggested for the commit message. And the same exact code
changes were around for two weeks. IMHO there's room for improvement,
so to speak.
> I hope that helps to clarify things.
It did to some extent, and thanks again for that.
next prev parent reply other threads:[~2017-08-25 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 20:52 [Intel-wired-lan] how to submit fixes for i40e/i40evf? Stefano Brivio
2017-08-25 20:52 ` Stefano Brivio
2017-08-25 22:10 ` [Intel-wired-lan] " Alexander Duyck
2017-08-25 22:10 ` Alexander Duyck
2017-08-25 22:28 ` Stefano Brivio [this message]
2017-08-25 22:28 ` Stefano Brivio
2017-08-28 17:00 ` Alexander Duyck
2017-08-28 17:00 ` Alexander Duyck
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=20170826002852.751d5f07@elisabeth \
--to=sbrivio@redhat.com \
--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.