All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH 00/14] lustre: fixes for many test failures
Date: Tue, 08 Jan 2019 10:09:56 +1100	[thread overview]
Message-ID: <877efgjc8r.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <alpine.LFD.2.21.1901072153570.24234@casper.infradead.org>

On Mon, Jan 07 2019, James Simmons wrote:

>> On Sun, Jan 06 2019, James Simmons wrote:
>> 
>> > This patch series contains mostly fixes to resolve the majority of
>> > the testing failures seen. Besides that are UAPI headers fixes to
>> > prepare for when lustre will leave the staging tree. Include Neil's
>> > dump_page_cache patch as well since it was landed in the OpenSFS
>> > branch and the migration of lu_objects to rhashtables depended on
>> > it.
>> 
>> Thanks - I've applied these.
>> I haven't received all of the PFL series yet ... 16,17,18 still in limbo
>> - so I haven't applied those yet.
>> When the stragglers here here, I suspect they'll all go in.
>
> Do you recieve patch 16,17,18 ? I do see they made it to the mailing list
> archive :

Yes, they arrived eventually, thanks.  The whole series seemed to be
coming in dribs and drabs ... some mail server somewhere must have been
a bit sick.

I'll have a look through them all today.

Thanks,
NeilBrown


>
> http://lists.lustre.org/pipermail/lustre-devel-lustre.org/2019-January/thread.html
>
> Also they are showing up at the patchwork site:
>
> https://patchwork.kernel.org/project/lustre-devel/list
>
> which is much easier to work with as a patch. Lastly if you need I can 
> send you those patches directly to you again. Let me know what you want.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20190108/e46e461e/attachment.sig>

      reply	other threads:[~2019-01-07 23:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 21:36 [lustre-devel] [PATCH 00/14] lustre: fixes for many test failures James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 01/14] lustre: llite: Add S_NOSEC support James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 02/14] lustre: llite: change how "dump_page_cache" walks a hash table James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 03/14] lustre: llite: add LL_IOC_FUTIMES_3 James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 04/14] lustre: llite: improve getdirstripe interface James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 05/14] lustre: uapi: fix lustre_user.h to C++ compatible James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 06/14] lustre: uapi: replace cfs_size_* macros with __ALIGN_KERNEL James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 07/14] lustre: uapi: final fixes for UAPI support James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 08/14] lustre: llite: op_data->op_valid is incorrect in ll_dir_getstripe James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 09/14] lustre: llite: return correct amount of bytes for short operations James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 10/14] lustre: llite: user xattr_prefix() to create xattr full name James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 11/14] lustre: llite: conditionally set it_flags in ll_file_open James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 12/14] lustre: llite: fix file migration James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 13/14] lustre: sysfs: temporary work around for sysfs naming James Simmons
2019-01-06 21:36 ` [lustre-devel] [PATCH 14/14] lustre: libcfs: hide struct cfs_cpt_table internals James Simmons
2019-01-07  5:17 ` [lustre-devel] [PATCH 00/14] lustre: fixes for many test failures NeilBrown
2019-01-07 21:57   ` James Simmons
2019-01-07 23:09     ` NeilBrown [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=877efgjc8r.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=lustre-devel@lists.lustre.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.