From: Dan Carpenter <dan.carpenter@oracle.com>
To: punit vara <punitvara@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
devel@driverdev.osuosl.org, Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Julia Lawall <Julia.Lawall@lip6.fr>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Subject: Re: [PATCH v2 4/4] Staging: rtl8712: fix warning for placing constant on the right side of test
Date: Thu, 22 Oct 2015 22:22:58 +0300 [thread overview]
Message-ID: <20151022192258.GQ7340@mwanda> (raw)
In-Reply-To: <CABXAfN+EHWki=BwTcx7tHzyxKo509jMM7eT5WzYVNXYAg2NvVw@mail.gmail.com>
On Fri, Oct 23, 2015 at 12:34:36AM +0530, punit vara wrote:
> I am working on linux-next .I have tried to rebase my local branch on
> your staging tree but I am getting too many conflict .and I have tried
> to clone your staging tree separately but due slow internet I am
> unable to clone it fully . Is there any other way I can get your
> staging tree by downloading ?
For a while, I had the worst internet of any kernel dev. I can help. :)
Do you have any complete kernel git repository? If you download it one
time then you just do a `git fetch` and `git checkout` after that.
Never do a `git pull`.
Downloading the linux kernel git repository the first time over bad
internet is a huge headache because if you lose the connection then you
have to restart. See if someone can post a .tar.gz of the kernel .git
directory on a webpage for you then you can download it bit by bit using
wget. Unpack it and do a `git reset --hard`.
regards,
dan carpenter
next prev parent reply other threads:[~2015-10-22 19:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 18:25 [PATCH RESEND 0/4] Staging: rtl8712: Fix coding style warnings Punit Vara
2015-10-14 18:25 ` [PATCH RESEND 1/4] Staging: rtl8712: Fix warning prefer eth_broadcast_addr() over memset() Punit Vara
2015-10-14 18:25 ` [PATCH v2 2/4] Staging: rtl8712: Use ether_addr_equal() over memcmp() Punit Vara
2015-10-14 18:25 ` [PATCH RESEND 3/4] Staging: rtl8712: Coding style warnings fix for block comments Punit Vara
2015-10-14 18:25 ` [PATCH v2 4/4] Staging: rtl8712: fix warning for placing constant on the right side of test Punit Vara
2015-10-17 5:16 ` Greg KH
2015-10-18 6:32 ` punit vara
2015-10-18 18:54 ` Tillmann Heidsieck
2015-10-18 19:14 ` Tillmann Heidsieck
2015-10-19 2:00 ` Greg KH
2015-10-19 2:44 ` Larry Finger
2015-10-19 15:21 ` punit vara
2015-10-22 19:04 ` punit vara
2015-10-22 19:14 ` Greg KH
2015-10-22 19:22 ` Dan Carpenter [this message]
2015-10-22 20:03 ` punit vara
2015-10-22 20:34 ` Dan Carpenter
2015-10-24 7:11 ` punit vara
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=20151022192258.GQ7340@mwanda \
--to=dan.carpenter@oracle.com \
--cc=Julia.Lawall@lip6.fr \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=punitvara@gmail.com \
--cc=sudipm.mukherjee@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.