From: Rich Johnston <rjohnston@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: linux-3.12 userspace
Date: Fri, 25 Oct 2013 12:55:03 -0500 [thread overview]
Message-ID: <526AB077.6030800@sgi.com> (raw)
In-Reply-To: <526A87F4.2020207@sandeen.net>
On 10/25/2013 10:02 AM, Eric Sandeen wrote:
> On 10/25/13 8:19 AM, Rich Johnston wrote:
>> Hey Folks,
>>
>> Dave Chinner has a 32 part userspace patchset that needs to be reviewed
>> and will be committed to coincide with the linux-3.12 kernel release.
I was referring to userspace ( hence the subject ;) ) matching kernel.
>>
>> Are there other userspace patches that support 3.12 kernel features that
>> need to be worked?
>>
>> All other patches on the list will be held back until the linux-3.13
>> merge window has opened.
>
> Are you talking about holding back kernelspace or userspace patches?
Only userspace.
>
> We'd want to get kernelspace merged in the xfs git tree well before
> the merge window,
Yup Ben is working on it.
> and I don't think the kernel merge window needs to
> affect userspace merges.
Umm yes I need to wait until the kernel supports the feature before
adding it to userspace. AFAIR the goal was to have userspace features
match the kernelspace.
>
> Can you talk in more specifics (which series/patches, for what codebase)
> you're proposing?
Yes I was referring to "[PATCH 00/32] xfsprogs: V5 write support for xfs_db"
http://oss.sgi.com/archives/xfs/2013-09/msg00805.html
Which needs to be reviewed before I can pull it in.
I was asking for any other userspace patches that need to be pulled in
for the next userspace release so it matches kernel 3.12.
>
> In general I think we simply have a review bottleneck, but once patchsets
> are reviewed, in general, they should just get merged, especially in userspace,
> IMHO.
>
No I was chastised for pulling in reviewed userspace patches too early.
Kernel code was not fully hashed out.
> But maybe I just need more details. :)
Am I still missing details?
>
> -Eric
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-10-25 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 13:19 linux-3.12 userspace Rich Johnston
2013-10-25 15:02 ` Eric Sandeen
2013-10-25 17:55 ` Rich Johnston [this message]
2013-10-28 2:23 ` Dave Chinner
2013-10-28 22:40 ` linux-3.12 userspace Take 2 Rich Johnston
2013-10-29 21:30 ` Eric Sandeen
2013-10-29 22:05 ` Dave Chinner
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=526AB077.6030800@sgi.com \
--to=rjohnston@sgi.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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