From: "Steve French" <smfrench@gmail.com>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: "Roel Kluin" <12o3l@tiscali.nl>,
sfrench@samba.org, linux-cifs-client@lists.samba.org,
samba-technical@lists.samba.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][fs/cifs/cifsfs.c] Make use of cifs_xquota_get
Date: Sat, 1 Mar 2008 12:29:53 -0600 [thread overview]
Message-ID: <524f69650803011029w50d16badkc52c2591c8113a99@mail.gmail.com> (raw)
In-Reply-To: <20080301161515.GD25835@cs181133002.pp.htv.fi>
On Sat, Mar 1, 2008 at 10:15 AM, Adrian Bunk <bunk@kernel.org> wrote:
> On Sat, Mar 01, 2008 at 10:06:11AM -0600, Steve French wrote:
> > There are quite a few fixes stuck in cifs-2.6.git that are fine to be
> > merged with mainline but didn't want to bug Linus with multiple merge
> > requests (there are a couple of more fixes that are not in
> > cifs-2.6.git pending review)
Just tried to check my cifs-2.6 tree on kernel.org and forward the merge
request off to Linus but it looks like the mainline tree has been rebuilt
(git diff shows "warning: no common commits"). Am syncing again.
> But generally please try to get fixes to Linus early - and having a few
> more weeks for getting fixes tested is more important than how often
> Linus pulls from you.
>
> > Thanks,
> >
> > Steve
>
> cu
>
>
> Adrian
>
> --
>
> "Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
> "Only a promise," Lao Er said.
> Pearl S. Buck - Dragon Seed
>
>
--
Thanks,
Steve
next prev parent reply other threads:[~2008-03-01 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 17:46 [PATCH][fs/cifs/cifsfs.c] Make use of cifs_xquota_get Roel Kluin
2008-03-01 9:37 ` Adrian Bunk
2008-03-01 16:06 ` Steve French
2008-03-01 16:15 ` Adrian Bunk
2008-03-01 18:29 ` Steve French [this message]
2008-03-01 18:40 ` Steve French
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=524f69650803011029w50d16badkc52c2591c8113a99@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=12o3l@tiscali.nl \
--cc=bunk@kernel.org \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).