From: Felipe Balbi <balbi@ti.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Robert Baldyga <r.baldyga@samsung.com>
Subject: Re: linux-next: manual merge of the usb-gadget tree with the vfs tree
Date: Thu, 18 Sep 2014 12:12:26 -0500 [thread overview]
Message-ID: <20140918171226.GE4537@saruman.home> (raw)
In-Reply-To: <20140917153400.GA8140@saruman.home>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
Hi,
On Wed, Sep 17, 2014 at 10:34:00AM -0500, Felipe Balbi wrote:
> On Wed, Sep 17, 2014 at 04:16:58PM +1000, Stephen Rothwell wrote:
> > Hi Felipe,
> >
> > Today's linux-next merge of the usb-gadget tree got a conflict in
> > drivers/usb/gadget/function/f_fs.c between commit 8322215aa91c ("f_fs:
>
> I can't find this commit on linux-usb. In fact, googling for it the only
> reference I find to that commit is this very thread. I would strong
> suggest that it be removed from the tree as it, apparently, went in
> without any review. Sure, it's a simple change, but it needs to be
> reviewed and needs to be sent to proper maintainers.
>
> Unless I'm missing something, of course, but I could not find any other
> references to this commit.
>
> Al, was this commit sent to any mailing list ?
a gentle ping here
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-18 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 6:16 linux-next: manual merge of the usb-gadget tree with the vfs tree Stephen Rothwell
2014-09-17 6:54 ` Robert Baldyga
2014-09-17 15:34 ` Felipe Balbi
2014-09-18 17:12 ` Felipe Balbi [this message]
2014-09-18 18:09 ` Al Viro
2014-09-18 18:16 ` Felipe Balbi
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=20140918171226.GE4537@saruman.home \
--to=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=r.baldyga@samsung.com \
--cc=sfr@canb.auug.org.au \
--cc=viro@ZenIV.linux.org.uk \
/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