From: Greg KH <greg@kroah.com>
To: Pavan Savoy <pavan_savoy@ti.com>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH] drivers:misc: ti-st: fix debugging code
Date: Thu, 3 Mar 2011 08:31:45 -0800 [thread overview]
Message-ID: <20110303163145.GA9418@kroah.com> (raw)
In-Reply-To: <8D0A8E9498DC4424BEA50A1B950A05FE@minx0099669>
On Thu, Mar 03, 2011 at 12:34:17PM +0530, Pavan Savoy wrote:
>
>
> >What tree was this made against? I can't seem to apply it to my
> >staging-next tree.
> >confused,
>
> Made against linux-next as usual.
> However I see that your staging-next has these for drivers/misc/ti-st/
>
> 73f12e8d3d94828b9efe2b8b8a34b4ad6d14ee47 drivers: misc: ti-st: fix review comments
> 2bb32e84a17fab547c7a746c7888e846c9cd88cc misc: ti-st: Kconfig & Makefile for TI_ST
> a0cc2f3b51a8649da5262aba7501dc21738e1b8d staging: ti-st: move TI_ST from staging to misc/
>
> and the linux-next has these for drivers/misc/ti-st/
>
> bb6a7d53d52ec5b574467c48159677904d34a56a drivers:misc: ti-st: fix debugging code
> 781a7395d239dbdb59738ca7fe08e71641bf583c drivers:misc: ti-st: remove multiple gpio handling
> 6d71ba2105a1d8c1712cdfcf46fc6040e4707cb9 drivers:misc: ti-st: fix hci-ll on wake_ind collision
> ef04d121f030329aae0c2d3ec22beea0c5cbcfd3 drivers:misc: ti-st: firmware download optimization
> 6710fcff66ef0330cdc458557271ee86026745d0 drivers:misc: ti-st: set right debug levels for logs
> 704426649dd4324b34cefea322f4333e5280f852 drivers:misc: ti-st: fix error codes
> ec60d0ad20ff8796dc41b30a9dce485478ccd263 drivers:misc: ti-st: move from rfkill to sysfs
> 5c88b02196a99332dacf305c8757674dd7a303ff drivers:misc: ti-st: register with channel IDs
> 73f12e8d3d94828b9efe2b8b8a34b4ad6d14ee47 drivers: misc: ti-st: fix review comments
> 2bb32e84a17fab547c7a746c7888e846c9cd88cc misc: ti-st: Kconfig & Makefile for TI_ST
> a0cc2f3b51a8649da5262aba7501dc21738e1b8d staging: ti-st: move TI_ST from staging to misc/
>
> So, I am not sure how the 8 patches on top of "drivers: misc: ti-st:
> fix review comments" made it to linux-next without making to
> staging-next ....
> when I received the automated mail of these 8 patches I got the tree link as
> "git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core-2.6.git" unlike the usual staging-next !!
>
> So make be you should apply them on driver-core-2.6 ?
> Can you help me understand the flow ?
Ah crap, I think I messed this up by applying the patches to the wrong
tree. I'll work out the issues and get it resolved later today.
Sorry for the noise, this is what I get for applying patches on long
flights...
greg k-h
next prev parent reply other threads:[~2011-03-03 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 9:59 [PATCH] drivers:misc: ti-st: fix debugging code pavan_savoy
2011-03-03 4:06 ` Greg KH
2011-03-03 7:04 ` Pavan Savoy
2011-03-03 16:31 ` Greg KH [this message]
2011-03-10 0:10 ` Greg KH
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=20110303163145.GA9418@kroah.com \
--to=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavan_savoy@ti.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