public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	Peter Karlsson <peter@zapto.se>,
	linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: staging patch not in staging tree (was: Re: [PATCH 1/2] staging: ft1000-usb: fixed table alignment)
Date: Tue, 23 Jun 2015 13:42:44 +0530	[thread overview]
Message-ID: <20150623081244.GA6096@sudip-PC> (raw)
In-Reply-To: <20150623080547.GI28762@mwanda>

On Tue, Jun 23, 2015 at 11:05:47AM +0300, Dan Carpenter wrote:
> On Tue, Jun 23, 2015 at 11:03:34AM +0530, Sudip Mukherjee wrote:
> > On Mon, Jun 22, 2015 at 07:06:49PM +0530, Sudip Mukherjee wrote:
> > > On Mon, Jun 22, 2015 at 03:02:37PM +0200, Peter Karlsson wrote:
> > > > On 2015-06-22 06:29, Sudip Mukherjee wrote:
> > > > > which tree have you been using?
> > > > > Greg will have three staging tree, use staging-testing
> > > > 
> > > > I have used linux-next tree :/
> > > well, I am now confused why linux-next is not having this struct.
> > > at line 415 of drivers/staging/ft1000/ft1000-usb/ft1000_debug.c
> > > struct timeval tv; is there in staging-next. And today's linux-next
> > > has merged staging-next. Then how that struct timeval is not there in
> > > linux-next ?
> > 
> > I was doing a bisect to see why the files are differing in staging-next
> > and linux-next. And it turns out to be:
> > 8b37bf430656 ("staging: ft1000: Replace timeval and time_t with time64_t")
> > 
> > which didn't go through the staging tree.
> > 
> 
> It's going through Arnd's tree since he does time stuff.  He should have
> sent it for an Ack or something.  Maybe he is planning to do that later.
> 
> The patch is very old.
> 
> Not a big deal?
there was no patch in ft1000 so its not a big deal. But will it not be
merge conflict when Linus tries to merge staging tree and Arnd's tree?

regards
sudip

  reply	other threads:[~2015-06-23  8:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21 11:29 [PATCH v2 0/2] checkpatch fixes Peter Karlsson
2015-06-21 11:29 ` [PATCH 1/2] staging: ft1000-usb: fixed table alignment Peter Karlsson
2015-06-22 11:30   ` Sudip Mukherjee
     [not found]     ` <20150622122900.GD1354@laptop>
     [not found]       ` <CADVatmP4mkHFYzmhML6AvKjgPny1bfi2e=n_=WAt6SruaH4zOw@mail.gmail.com>
     [not found]         ` <20150622124625.GE1354@laptop>
     [not found]           ` <CADVatmNJcjG_o6ro3LnHL8Q6myPfN5PWJ=oNcnFz6XHyjfZHgA@mail.gmail.com>
     [not found]             ` <20150622130237.GF1354@laptop>
     [not found]               ` <20150622133649.GB15439@sudip-PC>
2015-06-23  5:33                 ` staging patch not in staging tree (was: Re: [PATCH 1/2] staging: ft1000-usb: fixed table alignment) Sudip Mukherjee
2015-06-23  8:05                   ` Dan Carpenter
2015-06-23  8:12                     ` Sudip Mukherjee [this message]
2015-06-21 11:29 ` [PATCH 2/2] staging: ft1000-usb: shorten lines to under 80 characters Peter Karlsson

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=20150623081244.GA6096@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@zapto.se \
    /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