From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: Patch a file in the next branch
Date: Sun, 16 Sep 2012 10:58:39 +0200 [thread overview]
Message-ID: <20120916085839.GF25990@game.jcrosoft.org> (raw)
In-Reply-To: <20120916074457.GB6180@pengutronix.de>
On 09:44 Sun 16 Sep , Sascha Hauer wrote:
> On Sun, Sep 16, 2012 at 09:34:19AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 09:19 Sun 16 Sep , Franck Jullien wrote:
> > > Hi,
> > >
> > > In order to fix fat detection, I need to patch ff.c and filetype.c.
> > > However, ff.c is already patched in next (I need to modify the version
> > > already in next).
> > > Should I generate my patches against next or master ?
> > redo the patch as it more a v2 that an increment one
>
> Probing a FAT with MBR is a new feature, being able to automatically
> detect it is a new feature aswell, so I see no reason to merge both
> patches.
yes but without it the mount will ne to force the type
and As discuss with Franch the ff.c should use the filetype so make in one
patch make more sense
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-09-16 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-16 7:19 Franck Jullien
2012-09-16 7:26 ` Sascha Hauer
2012-09-16 7:34 ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-16 7:44 ` Sascha Hauer
2012-09-16 8:58 ` Jean-Christophe PLAGNIOL-VILLARD [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=20120916085839.GF25990@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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