public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi@etezian.org>
To: Steve French <smfrench@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-cifs@vger.kernel.org, Andi Shyti <andi@etezian.org>,
	mikko.rapeli@iki.fi
Subject: Re: [PATCH 2/2] cifs: file: initialize oparms.reconnect before using it
Date: Mon, 29 Jul 2013 10:33:25 +0200	[thread overview]
Message-ID: <20130729083325.GA1948@jack.whiskey> (raw)
In-Reply-To: <CAH2r5msP8+qZnb38Rj5WMWmqWFtopmoe671G6TNTB=61BvYEnA@mail.gmail.com>

Hi Steve,

> Your patch looks reasonable.   Would you repost the patch to
> linux-cifs mailing list (and add any additional reviewers or testers
> if you would like if you got feedback)?

Thanks for your mail,

Actually linux-cifs is on CC and this is the output of
get_maintainer:

Steve French <sfrench@samba.org> (supporter:COMMON INTERNET F...)
linux-cifs@vger.kernel.org (open list:COMMON INTERNET F...)
samba-technical@lists.samba.org (moderated list:COMMON INTERNET F...)
linux-kernel@vger.kernel.org (open list)

All are on CC. get_maintainers, indeed sometimes is not very
precise since gets the CC list by doing a git blame on the file
and adding the ones who previously modified the specific lines.

If this patch got lost I could enrich my To/Cc list by looking at
git shortlog and more carefully at git blame.

Thanks,
Andi

  reply	other threads:[~2013-07-29  8:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  3:40 [PATCH 2/2] cifs: file: initialize oparms.reconnect before using it Steve French
2013-07-29  8:33 ` Andi Shyti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-07-22 19:24 Andi Shyti
2013-07-22 19:26 ` Andi Shyti

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=20130729083325.GA1948@jack.whiskey \
    --to=andi@etezian.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikko.rapeli@iki.fi \
    --cc=smfrench@gmail.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