From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Mar 22
Date: Fri, 23 Mar 2012 09:19:00 +1100 [thread overview]
Message-ID: <20120323091900.d3c007d76b49d4053457906e@canb.auug.org.au> (raw)
In-Reply-To: <4F6B88D2.5060500@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Hi Mauro,
On Thu, 22 Mar 2012 17:17:22 -0300 Mauro Carvalho Chehab <mchehab@redhat.com> wrote:
>
> Em 22-03-2012 03:08, Stephen Rothwell escreveu:
> > Merging edac/linux_next (4d096ca MAINTAINERS: add an entry for Edac Sandy Bridge driver)
>
> Not sure what's happening, but I've updated my EDAC tree a few days ago,
> and I've added more stuff yesterday, but you're still pointing to an
> old changeset.
>
> Could you please check if it is pointing to the right tree/branch? It should be:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-edac.git linux-next
Well, I am still using the infradead.org repo. I will start using the
above today. (and it looks like the branch is actually linux_next)
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-22 22:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 6:08 linux-next: Tree for Mar 22 Stephen Rothwell
2012-03-22 20:17 ` Mauro Carvalho Chehab
2012-03-22 22:19 ` Stephen Rothwell [this message]
2012-03-23 0:03 ` Mauro Carvalho Chehab
2013-03-22 5:04 Stephen Rothwell
2013-03-22 5:04 ` Stephen Rothwell
2016-03-22 3:25 Stephen Rothwell
2017-03-22 4:20 Stephen Rothwell
2018-03-22 8:38 Stephen Rothwell
2019-03-22 3:36 Stephen Rothwell
2021-03-22 7:52 Stephen Rothwell
2022-03-22 9:38 Stephen Rothwell
2023-03-22 1:35 Stephen Rothwell
2024-03-22 2:00 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=20120323091900.d3c007d76b49d4053457906e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@redhat.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.