public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Maiolino <cmaiolino@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Kaho Ng <ngkaho1234@gmail.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [PATCH v2] xfs: indentation fix in xfs_btree_get_iroot()
Date: Wed, 22 Jun 2016 10:23:32 +0200	[thread overview]
Message-ID: <20160622082332.GH28212@redhat.com> (raw)
In-Reply-To: <20160622063943.GU12670@dastard>

On Wed, Jun 22, 2016 at 04:39:43PM +1000, Dave Chinner wrote:
> On Wed, Jun 22, 2016 at 12:11:37PM +0800, Kaho Ng wrote:
> > The indentation in this function is different from the other functions.
> > Those spacebars are converted to tabs to improve readability.
> > 
> > Signed-off-by: Kaho Ng <ngkaho1234@gmail.com>
> > ---
> >  fs/xfs/libxfs/xfs_btree.c | 8 ++++----
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> > 
> > diff --git a/fs/xfs/libxfs/xfs_btree.c b/fs/xfs/libxfs/xfs_btree.c
> > index 1f88e1c..4f84dde 100644
> > --- a/fs/xfs/libxfs/xfs_btree.c
> > +++ b/fs/xfs/libxfs/xfs_btree.c
> > @@ -543,12 +543,12 @@ xfs_btree_ptr_addr(
> >   */
> >  STATIC struct xfs_btree_block *
> >  xfs_btree_get_iroot(
> > -       struct xfs_btree_cur    *cur)
> > +	struct xfs_btree_cur	*cur)
> >  {
> > -       struct xfs_ifork        *ifp;
> > +	struct xfs_ifork	*ifp;
> >  
> > -       ifp = XFS_IFORK_PTR(cur->bc_private.b.ip, cur-
> > >bc_private.b.whichfork);
> > -       return (struct xfs_btree_block *)ifp->if_broot;
> > +	ifp = XFS_IFORK_PTR(cur->bc_private.b.ip, cur-
> > >bc_private.b.whichfork);
> > +	return (struct xfs_btree_block *)ifp->if_broot;
> >  }
> 
> That's better, but your mailer is still doing weird things to the
> patch. It line wrapped it this time, and converted all the spaces to
> some wierd multi-byte character instead of a plain ascii space.
> 
> What you should do is send the patch to yourself, extract it from
> the email you receive, and try to apply it to a clean tree. If you
> can do that, then the patch is not getting mangled when you send it.
> See Documentation/SubmittingPatches and
> Documentation/email-clients.txt for help.
> 

This is a problem when sending patches from a gmail account. It's converted to a
base64 format, instead of pure clean text.

I'd setup git to send the patch through the gmail smtp using git send-email. So
it won't screw up with the file format. Well, at least, that's what I do when I
need to send patches through a gmail account :)

-- 
Carlos

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-06-22  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22  4:11 [PATCH v2] xfs: indentation fix in xfs_btree_get_iroot() Kaho Ng
2016-06-22  6:39 ` Dave Chinner
2016-06-22  8:23   ` Carlos Maiolino [this message]
2016-06-22 10:30     ` Kaho Ng

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=20160622082332.GH28212@redhat.com \
    --to=cmaiolino@redhat.com \
    --cc=david@fromorbit.com \
    --cc=ngkaho1234@gmail.com \
    --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