linux-kernel - Re: [GIT PULL] AMD64 EDAC module for 2.6.31

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090612100308.GA4403@aftab>
Date:	Fri, 12 Jun 2009 12:03:08 +0200
From:	Borislav Petkov <borislav.petkov@....com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Borislav Petkov <petkovbb@...glemail.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] AMD64 EDAC module for 2.6.31

On Fri, Jun 12, 2009 at 06:10:22PM +1000, Stephen Rothwell wrote:
> Hi Borislav,
> 
> On Fri, 12 Jun 2009 10:03:23 +0200 Borislav Petkov <petkovbb@...glemail.com> wrote:
> >
> > now that amd64 EDAC is upstream, I've removed the fox-next branch since
> > the next patch series is not ready yet.
> > 
> > What is actually the proper way to let you know that I don't have any
> > more patches for linux-next right now and that you don't have to pull
> > from my repo for now?
> 
> Just set the for-next branch to point somewhere in Linus' tree (where it
> was would be fine if that is what Linus' merged from you).  That way I
> can still try to fetch it each day and when you have new stuff, you can
> just put it there without bothering to remember to tell me anything.

Thanks, done.

-- 
Regards/Gruss,
Boris.

Operating | Advanced Micro Devices GmbH
  System  | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany
 Research | Geschäftsführer: Thomas M. McCoy, Giuliano Meroni
  Center  | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
  (OSRC)  | Registergericht München, HRB Nr. 43632

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/