From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Feb 1
Date: Mon, 1 Feb 2016 12:51:28 +0530 [thread overview]
Message-ID: <20160201072128.GA8182@sudip-pc> (raw)
In-Reply-To: <20160201171432.76038f05@canb.auug.org.au>
On Mon, Feb 01, 2016 at 05:14:32PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160129:
blackfin defconfig fails, and it needs
https://patchwork.kernel.org/patch/8148161/
regards
sudip
next prev parent reply other threads:[~2016-02-01 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 6:14 linux-next: Tree for Feb 1 Stephen Rothwell
2016-02-01 7:21 ` Sudip Mukherjee [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 3:32 Stephen Rothwell
2023-02-01 4:20 Stephen Rothwell
2022-02-01 4:33 Stephen Rothwell
2021-02-01 9:14 Stephen Rothwell
2019-02-01 5:41 Stephen Rothwell
2018-02-01 4:47 Stephen Rothwell
2017-02-01 7:28 Stephen Rothwell
2012-02-01 6:16 Stephen Rothwell
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=20160201072128.GA8182@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).