From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Hannes Reinecke <hare@suse.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
oss-drivers@netronome.com
Subject: Re: [PATCH] aic7xxx: fix firmware build with O=path
Date: Tue, 18 Jul 2017 21:45:49 -0400 [thread overview]
Message-ID: <yq1wp75b3n6.fsf@oracle.com> (raw)
In-Reply-To: <20170718183536.35e00175@cakuba.netronome.com> (Jakub Kicinski's message of "Tue, 18 Jul 2017 18:35:36 -0700")
Jakub,
> I just noticed this patch got marked as "Deferred, archived" in
> patchwork. I'm not entirely sure by whom and why? Could someone
> explain what is the issue? I would really appreciate if we could
> merge this patch and have this driver not break builds randomly...
It's an indication that the patch sat around without any reviews for way
too long.
People generally don't go chasing around in their mail archives for
several week old patches to review. The best thing to do for patches I
mark as deferred is to resubmit them so they get back on people's radar.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-07-19 1:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 4:17 [PATCH] aic7xxx: fix firmware build with O=path Jakub Kicinski
2017-07-04 0:29 ` Jakub Kicinski
2017-07-19 1:35 ` Jakub Kicinski
2017-07-19 1:45 ` Martin K. Petersen [this message]
2017-07-19 1:52 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2017-07-19 1:58 Jakub Kicinski
2017-07-21 18:51 ` Jakub Kicinski
2017-07-24 7:00 ` Hannes Reinecke
2017-07-24 21:14 ` Jakub Kicinski
2017-07-25 2:07 ` Martin K. Petersen
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=yq1wp75b3n6.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=hare@suse.com \
--cc=jakub.kicinski@netronome.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=oss-drivers@netronome.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox